From: Winston W. <win...@ca...> - 2005-01-29 14:44:18
|
I've been thinking about future directions for Webware and WSGIKit. =20 What do you think about shifting Webware into a WSGI container, with=20 WSGIKit as one possible containee? Advantages would be greater=20 separation of concerns, and easier testing. Perhaps more flexibility=20 if lots of WSGI clients become available. Here are the responsiblities of Webware that I can come up with. The=20 first five would be handled by the Webware container, and the last=20 three would be handled by the WSGI "client" if that's the proper term. =95 Interface with Apache or provide built-in web server =95 Decode URIs and choose the servlet to call =95 Contain broken pages so it doesn't break the rest of the = site =95 Produce error reports when pages break. =95 Speed development by auto-reloading when source has changed. =95 Manage sessions =95 Build an HTTP response with headers, cookies, and so forth. =95 Write HTML Comments? _________________________________________ winston wolff - (646) 827-2242 - http://www.stratolab.com - learning by=20= creating= |