A couple things I don't understand in this discussion.
Phillip J. Eby said:
> At 03:28 AM 7/17/2005 -0500, Ian Bicking wrote:
>>I guess I'm treating the request environment as that context. I don't
>>really see the problem with that...?
>
> It puts a layer in the request call stack for each servi
Graham Dumpleton wrote:
> My understanding from reading the WSGI PEP and examples like that above is
> that the WSGI middleware stack concept is very much tree like, but where at
> any specific node within the tree, one can only traverse into one child.
> Ie.,
> a parent middleware component could
Chris McDonough wrote:
> On Sun, 2005-07-17 at 03:16 -0500, Ian Bicking wrote:
>
>>This is what Paste does in configuration, like:
>>
>>middleware.extend([
>> SessionMiddleware, IdentificationMiddleware,
>> AuthenticationMiddleware, ChallengeMiddleware])
>>
>>This kind of middleware takes
Ian Bicking wrote ..
> There's several conventions that could be used for trying applications
> in-sequence. For instance, you could do something like this (untested)
> for delegating to different apps until one of them doesn't respond with
> a 404:
>
> class FirstFound(object):
> """Try app
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-bran
