On Thu, May 7, 2009 at 3:37 AM, Kless <[email protected]> wrote: > > This would let share and reuse applications used with Werkzeug and > frameworks based on it. And the most important is that would speed up > the grow up of the community. >
Werkzeug already provides easy paths for extending the functionality in two layers: _1_ middleware _2_ application (1) This isn't specific to werkzeug, this is just WSGI. So writing a WSGI middleware allows affords you integration with an app based on werkzeug of any other WSGI app (django, turbogears, etc.). Albeit, sometimes hacks if the target framework does things wrong: http://dev.pocoo.org/projects/werkzeug/wiki/UsingDebuggerWithDjango (2) At the application level their isn't a special plugin API - which is a good thing, IMO. You can extend the functionality either through writing more functions or utilty classes or Request/Response mixins (http://werkzeug.pocoo.org/documentation/dev/wrappers.html#mixin-classes). You might consider contributing to the project if it's generally useful: http://dev.pocoo.org/projects/werkzeug/browser/werkzeug/contrib. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" 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/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
