[openstack-dev] Pecan vs Falcon?
doug.hellmann at dreamhost.com
Wed Apr 24 15:04:58 UTC 2013
On Wed, Apr 24, 2013 at 7:04 AM, John Dickinson <me at not.mn> wrote:
> Other can chime in with their reasons, but the two biggest reason for me
> 1) WebOb's tendency to break in a backwards-incompatible way with many
> releases. Looking at v 1.0.8 to version 1.2.x was painful
That has been true in the past. My understanding is that the issues that
caused the breakage have been resolved.
> 2) WebOb has lots of "magic" that makes it hard to figure out what's going
> on. Specifically, setting and reading many attributes ended up calling
> getters and setters that also affected headers on the request or response.
> For example, properly setting a content-type and a charset on a response
> object does lots of magic that ends up making it hard for a developer to
> clearly see what's actually going to be in the response
Yes, it's complex. See the earlier comments about edge cases and "poorly
> A smaller benefit to replacing WebOb with an internal module is that it
> removes a dependency for deployers and packagers.
WebOb is already widely used and included in the distributions.
> On Apr 24, 2013, at 6:20 AM, Kurt Griffiths <kurt.griffiths at rackspace.com>
> >> ...there's a huge community around WebOb and they have all
> >> implicitly agreed to contribute back solutions to issues
> >> that come up.
> > Why did Swift move away from WebOb? Are they planning to go
> > Back to using it at some point?
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev