Yes...
- Configuration. The design and implementation of a clean
configuration format would really make WSGIKit usable.
BTW, I have written a config parser with WSGIKit in mind, but I haven't plugged it into anything yet. I described some of the features here: http://blog.ianbicking.org/2005-01-wsgikit-config.html
In some ways it bothers me because it's a bit complicated, but each point of complication is also a feature I think would be really useful, so it's hard to say. It includes a fair number of unit tests.
- Better exception handling. Perhaps the specific behavior (e.g.
logging vs. dumping all data to the browser) would be governed by
the configuration system.
I've also been investigating different exception reporters, so the tracebacks can be more useful. So far I've looked at:
PyCrash: http://pycrash.sourceforge.net/
Mongoose: http://themongoose.sourceforge.net/
Zope includes an exception formatter as well, that doesn't carry any Zope dependencies; but it looks for __traceback_info__ local variables which is an easy way to annotate the traceback.
py: http://codespeak.net/py/current/doc/ -- includes a really thorough exception formatter, but not as a seperate component
I'm not sure if Mongoose is multi-thread aware, it looks like its settings are process-wide, which isn't what I want. But it has some good ideas -- I like the incident identifier. PyCrash is kind of XMLish and maybe even Javaish.
-- 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
