1 Introduction
2 ------------
3
4 WebStack is a package which provides a common API for Python Web applications,
5 regardless of the underlying server or framework environment. It should be
6 possible with WebStack to design and implement an application and to choose a
7 deployment environment, without having to go back and rewrite large parts of
8 that application to work in the chosen environment or in other environments
9 (should the deployment requirements change after the application has been
10 written).
11
12 Framework Support
13 -----------------
14
15 Currently, BaseHTTPRequestHandler (via BaseHTTPServer in the standard library),
16 CGI, Jython/Java Servlet API, mod_python, Twisted and Webware are supported.
17 Each framework has its own set of strengths and weaknesses, but the idea is that
18 deployment concerns can be considered separately from the implementation of
19 application functionality. Consult the NOTES.txt files in each framework's
20 subdirectory of the docs directory for some notes on how applications may be run
21 in each environment.
22
23 Tested Frameworks
24 -----------------
25
26 BaseHTTPRequestHandler Python 2.2.2, Python 2.3.3
27 CGI Apache 2.0.44
28 Jython/Java Servlet API Jython 2.1, Java JDK 1.3.1_02, Tomcat 4.1.27 (Servlet 2.3)
29 mod_python 3.0.3 (3.1.3 for cookie support)
30 Twisted 1.0.5
31 Webware 0.8.1, CVS (2004-02-06)
32 Zope 2.7.2-0
33
34 New in WebStack 0.7 (Changes Since WebStack 0.6)
35 ------------------------------------------------
36
37 Fixed file upload semantics.
38 Fixed content type handling (although some improvement remains).
39 Introduced Zope 2 support.
40
41 New in WebStack 0.6 (Changes Since WebStack 0.5)
42 ------------------------------------------------
43
44 Introduced Jython/Java Servlet API support.
45 Minor fixes to example applications and to BaseHTTPRequestHandler.
46
47 New in WebStack 0.5 (Changes Since WebStack 0.4)
48 ------------------------------------------------
49
50 Changed request body fields/parameters so that they are now represented using
51 Unicode objects rather than plain strings.
52 Introduced better support for Unicode in response streams.
53
54 New in WebStack 0.4 (Changes Since WebStack 0.3)
55 ------------------------------------------------
56
57 Added application definition of user identity, permitting alternative
58 authentication mechanisms.
59 Improved BaseHTTPRequestHandler and mod_python reliability around fields from
60 request bodies.
61 Provided stream and environment parameterisation in the CGI adapter.
62 Added LoginRedirect and Login examples.
63 Added get_path_without_query and fixed get_path behaviour.
64
65 New in WebStack 0.3 (Changes Since WebStack 0.2)
66 ------------------------------------------------
67
68 Added better header support for Webware (suggested by Ian Bicking).
69 Introduced CGI and Java Servlet support (the latter is currently
70 broken/unfinished).
71 Introduced support for cookies.
72
73 Future Work
74 -----------
75
76 Things to consider for future releases: improved cookie support, redirects,
77 session interfaces, access to shared resources and much better documentation.
78
79 Field access needs testing, especially for anything using the cgi.FieldStorage
80 class - Webware and Twisted certainly need reviewing. The acquisition of
81 fields from specific sources should be made more strict - some frameworks (eg.
82 mod_python) provide path fields in the body fields dictionary.
83
84 Cookie objects need defining strictly, especially since the standard library
85 Cookie object behaves differently to mod_python (and possibly Webware) Cookie
86 objects. Moreover, the set_cookie_value method needs to provide access to the
87 usual cookie parameters as supported by the frameworks.
88
89 Release Procedures
90 ------------------
91
92 Update the WebStack/__init__.py __version__ attribute.
93 Update the release notes (see above).
94 Check the setup.py file and ensure that all package directories are mentioned.
95 Tag, export, archive, upload.