<% header(name + ' 0.2 Release Notes') %>
Webware for Python 0.2
Release Notes
- Version 0.2 was released on 5/12/2000.
- In general, 0.1 was more of a conceptual release than anything else. While 0.2 still has it's share of problems, you actually have a chance of writing something. :-)
- There have been lots of improvements to the classes in terms of refining their interface, fleshing out their functionality and just plain making them work. Most details are not documented here, because no one had an application written in 0.1. Only the most notables are below:
- Component and HTTPComponent became Servlet and HTTPServlet.
- Created Page class, a convenient subclass of HTTPServlet.
- Renamed Context to Transaction, which is a more accurate name.
- Created root class Object for the entire kit.
- Got sessions working.
- Got incoming and outgoing cookies working.
- Created classes ServletFactory, PythonServletFactory and PSPServletFactory and reworked Application.createServletInContext() accordingly.
- Added support for config files for AppServer and Application.
- Activity logging. (See Logs/Activity.csv or the _admin page).
- Error/exception handling: log the error, display a public error message, save a private error message and e-mail that private error message.
- Created Admin page (_admin). Servlets that start with _ are considered to reside with the app server. Created _dumpCSV and _dumpErrors to support/implement the admin pages.
- If a Servlet's file is updated, the Servlet gets reloaded by the Application. This substantially reduces the need to restart the server. However, this does not handle changes to the Application or changes to the Servlet's ancestor classes.
- Responses are no longer delivered through stdout, but through a string returned by contents(). That means that print statements show up in the console and can be used for debugging.
- The app server now writes its host name and port to address.text which is automatically picked up by the adaptors.
- Added support for config setting 'Multitasking' which can be threading, forking, or sequencing. Forking is slower than the other two. Threading servers multiple users better. Threading is the default.
- Incorporated Jay Love's FastCGIAdaptor.
- Expanded the examples and documentation.
<% footer() %>