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