I'd like to do some cleaning up of Webware after our v0.9 build. The automated tests are good preparation to that cleanup. When there are a good set of test cases in place, I'd like to make Webware easier to install. I'm also improving my Cheetah ServletFactory which I can add as a kit. And I have a very simple script that functions like Ant or make--it's a place to put short scripts when developing such as "generate MiddleKit sql", "run sql on my database", "clean up temporary files", "run python interactively with the same python path as the appserver", "upload my web application to the production server." "run webware, but using the CVS version instead of v0.81"
What improvements would other people like? I will compile a list and post it on the wiki. I'll also sort it in priority order as judged by the enthusiastic responses on this list.
29 Dec 04 - Ian Bicking - While we're talking about improvements, I might re-note the existance of WSGIKit.
04 Jan 05 - Tom Schwaller - Are Aspects (simple solution in CherryPy) something people would like to see integrated in Webware? Or are continuations? Maybe using generators and annotations could make Webware much more sophisticated?
- 19 Feb 05 - Lloyd
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;
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? :-)
WSGIKit - Should it be developed in parallel, or should the old Webware be dropped? There are several votes for keeping them in parallel.