I'd be up for a WSGIKit sprint. I certainly don't understand WSGIKit as well as I understand Webware so this is a good opportunity to get my feet wet.
I'd like to work on making it a viable development platform first. So my priorities would be:
* unit tests,
Certainly.
* exception handling,
Definitely; there's a simple exception handler middleware based on cgitb, but since it's such a central part of the experience and deployment I'd like for it to be better.
* restarting when source is changed.
This is hard, since it's up to the server when to restart. I'm not sure how it would work.
For logging, shouldn't we use Python's built-in logging facility?
Yes, but there's a lot of glue necessary to use that module -- we'd want to separate out different kinds of logs (error logs, debug logs, traffic logs) and make it all configurable. Which gets back to configuration, which is pretty important to all this and quite missing from WSGIKit at this point.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
