voltron wrote: > Hi Ian! > > Do you have a break down list of the benefits of using WebOb? > Do you have a simple example of how one would use WebOb with an > existing Pylons app? > Should one start coding new applications with respect to WebO?
The benefits are mostly just that it's a more complete mapping of HTTP than the existing request object, and so it makes some things a bit easier. E.g., all the date-related headers are parsed for you. You shouldn't start using it now, as I really just want some feedback on it before the API is settled. Then probably it would be most useful to use in framework-neutral middleware, as it makes it a bit more compact to write that middleware. At some point hopefully Pylons can move over to it, probably without many issues since the API is a superset of the existing API. I wouldn't recommend moving individual apps over now, though. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org : Write code, do good : http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
