On Mon, 2005-07-18 at 22:49 -0500, Ian Bicking wrote:
In addition to the examples I gave in response to Graham, I wrote a
document on this a while ago:
http://pythonpaste.org/docs/url-parsing-with-wsgi.html
The hard part about this is configuration; it's easy to configure a
non-branching
Chris McDonough wrote:
On Mon, 2005-07-18 at 22:49 -0500, Ian Bicking wrote:
In addition to the examples I gave in response to Graham, I wrote a
document on this a while ago:
http://pythonpaste.org/docs/url-parsing-with-wsgi.html
The hard part about this is configuration; it's easy to
Phillip J. Eby wrote:
In many cases, the middleware is modifying or watching the
application's output. For instance, catching a 401 and turning that
into the appropriate login -- which might mean producing a 401, a
redirect, a login page via internal redirect, or whatever.
And that
While I'm not following every detail of this discussion, this line caught
my attention -
Ian Bicking said:
Really, if you are building user-visible standard libraries, you are
building a framework.
only because Fowler recently posted something that made me think about
this, where he
(b)
Have chain application = authmiddleware(fileserverapp)
Use Handlers, as Ian suggested, and in the fileserverapp's init:
Handlers(
IfTest(method=GET,MimeOkForGzip=True, RunApp=gzipmiddleware(doGET)),
IfTest(method=GET,MimeOkForGzip=False, RunApp=doGET),
