On 11/5/05, Luke Plant <[EMAIL PROTECTED]> wrote: > I agree that functionality shouldn't be added until we have a use case, > and the concept of walking up and down the stack helps. It's not quite > that simple though -
Hmm... I thought the handlers did the right thing, damn :-( > Solutions: > 1) allow different ordering for request and response middleware If this is the solution, we should go all the way, and expose the four different middleware lists directly. > 2) call this a bug in the CacheMiddleware, and make process_response > return the one it got out of the cache, not "cache plus middleware" I don't see how the cache-middleware can be at fault here, unless you want it to return the cached response in process_response. This doesn't stop the other response middlewares from running, which I think they shouldn't at all. > 3) implement the stack of middleware as you described it, which would > solve this problem, but I don't know if it might introduce some others. +1 from me. /s
