On 27/05/07, Robert Brewer <[EMAIL PROTECTED]> wrote: > > > > Graham Dumpleton wrote: > > The problem then as above is what does one do at > > the boundary between a WSGI application and the > > web server hosting it? Do you just always assume > > a WSGI application provides an error page, or allow > > some way that a WSGI application can defer to the > > web server the task of generating an error page > > instead? > > The web server should not be trying to correct what > the application gives it, except as absolutely necessary > to get the response on the wire, or obey the HTTP spec > (and even that's questionable). If you want consistent > error pages across an entire application or site, write > a piece of WSGI middleware which does that and explicitly > include it in your middleware graph.
Your thinking just WSGI though. The whole thing with Apache is that it is possible to bring together application components from many different sources. Thus Apache in this case is more than just a web server but an application framework itself in some ways. Ie., your application could be a combination of CGI scripts written in Perl, Python etc, handlers or page templating systems making use of PHP, mod_perl, mod_python etc, as well as WSGI components. Apache already provides ways for all these components to be able to signal that the error page generation be done by the Apache core so it is consistent, but the way that WSGI is defined one can't use it. Thus, I am looking at the bigger picture of those people who want to use Apache as a the framework for building a web application and who don't want to restrict themselves to just Python and WSGI. Graham _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
