Hi. First time caller. We're studying WSGI and Pylons as a likely environment to which to port existing applications and framework. In our current environment, we often have 2 or more applications running under a single process, where an "app manager" object sequentially offers the request to each application, until one claims and handles it.
There is an existing WSGI middleware piece named Cascade that appears to work similarly, and could be a candidate approach; however, it uses 404 responses from the applications as its signal to keep looking. In our design, 404 responses have a different meaning: that the application has accepted the URL pattern as being its own, and is deliberately stating that a specific document or resource is not found. Thus we would specifically not want to pass the request on to other apps when a 404 is returned. Is this "404 messaging" approach really needed? Or more specifically, does a WSGI application need to respond at all? Maybe instead it simply never calls the start_response callable and just returns None. If the app manager could then examine whether start_response was called, and use that information to decide whether to pass on to the next app. (If no app starts a response, the app manager then issues the 404.) Thanks for any responses. I'm new to WSGI, but find it quite appealing. Randy Pearson [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 -~----------~----~----~----~------~----~------~--~---
