On Mon, Jan 10, 2011 at 11:24 AM, Daniel Holth <[email protected]> wrote:
> WSGI is not the right layer for composing applications.
Most WSGI framework developers have come to the conclusion that
middleware is not all it's cracked up to be. The WSGI protocol is
clunky and you have to do weird things to share data between layers.
Route middleware, session middleware, and database middleware were
good experiments but they showed this is not the best place for those.
With Pyramid's event system you can plug in code at the beginning and
end of every request and at other times, which can perform tasks
otherwise done by Pylons BaseController.__call__ or middleware.
The developers tried for three or four years to streamline the WSGI
protocol ("WSGI 2") but could never get consensus, and now there's a
realization that just turning away from WSGI may be better. Not to
eliminate WSGI in its basic purpose (connecting to a Python
webserver), but to use other protocols for other stuff: WebOb, Pyramid
components, etc.
--
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.
