On 8/9/07, Ian Bicking <[EMAIL PROTECTED]> wrote: > > 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.
The biggest benefit is it standardizes the request/response across all the frameworks that use it. This avoids you having to learn a different syntax for each framework, as well as their different limitations/bugs. It's part of the movement that produced WSGI, Paste, and Pylons in the first place. Of course, frameworks may have to put a translation layer on top of it, either for backward compatibility, API ideology, or additional features. But a thin layer on top of a standard way of doing things is better than a completely different implementation in each framework. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
