Mike thanks for great post again, For now I use 1) but maybe will think about webob after my product released.
> I have been thinking about a heresy the past week, that instead of > improving WSGI maybe we should just leapfrog it to a WebOb-based chain > of servers, applicaiions, and middleware. Then the protocol could > just create the request/response once a the beginning of the chain and > let the middleware/application modify it rather than each middleware > having to reinvent the wheel and parse obscure environ keys. But > that's too radical to just do in Pylons right now. > That is exactly what is done in J2EE ServeltFilter, request/response get created and passed to the chain of filters, Filters are mapped to some URLs or Servlets (controllers in Pylons world). I think it worth considering something similar with Pylons in the future. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
