List of things to do

Short- to medium-term

Long-term/miscellaneous

Migration to C API

PyWX is moving away from AOLserver's Tcl API and instead using its C API. But this transition is still in progress. So the remaining modules (e.g., ns_db.py) that are built on the Tcl API should be rewritten.

Better factorization

It would be great to factor the functionality of PyWX better between essential components and extra features. For example, ns_python.py contains a dog's breakfast of routines for several unrelated purposes.

More flexible configuration

Allow some of the configuration choices to be made on a script-by-script level. For example, CGI emulation might be needed for just a few scripts in a system. Allowing some options to be passed to ns_python exec, like maybe
ns_python exec [ -attachstdio | -cgienv
                 | -cachecode | -reuseinterpreter ] "<pythoncode>"
would suffice, at least for the registry-based method of invoking PyWX.

Benchmarking

One of the selling points of AOLserver/PyWX is its performance. We should produce some benchmarks for pages per second to ensure that PyWX is doing well. We should include a comparison of performance under various combinations of configuration options, and with and without database access. [mhagger: I have gotten about 150 pages/s on a Pentium 500 for test-api.py.]

Cool ideas

Better documentation!

In particular,

Web site!

In particular,

Future Projects