is that a good thing (contexts going away)?
Either they should go away, or become a mechanism for web applications. Right now they don't do anything but cause complexity.
recently i was looking over the (abandoned?) "webware experimental refactoring" project, and it had some interesting improvements that, to me, seemed like a natural progression for webware:
- contexts become "applications" - get their own sessions and state;
- multiple applications/contexts can run under a single server instance;
Hmm, I never looked in there.
improvements to webware after 0.9 -
- formalized method for executing (context/)application-specific code once on startup, with access to various webware components. (what's the recommended way to do this now? stick it in a site page at module level?)
Yes, that's a good idea.
- out-of-the-box connection pooling
Wouldn't this depend on what you are using to save things in your DB? E.g. MiddleKit has it's own pooling mechanism.
- get webware into debian's repository? :-)
these are suggestions from a lowly webware user, not a webware developer... take them for what they're worth...
They are very useful. I've added them to the wiki list:
http://wiki.w4py.org/featuresafterv09.html
_________________________________________
winston wolff - (646) 827-2242 - http://www.stratolab.com - learning by creating
