Ian Bicking wrote:
> I'm personally convinced that this should be the future of Webware (and,
> in a general architectural sense, Python web programming as a whole). It
> offers a few current advantages over Webware:
> * Mostly backward-compatible. There are some missing corners of the
> Webware API, but that can be fixed. The whole MakeAppWorkDir thing goes
> away (for better or worse), and Contexts disappear.
is that a good thing (contexts going away)?
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;
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?)
- out-of-the-box connection pooling
- 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...