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
16 library), CGI, Jython/Java Servlet API, mod_python, Twisted, Webware and Zope
17 2 are supported. Each framework has its own set of strengths and weaknesses,
18 but the idea is that deployment concerns can be considered separately from the
19 implementation of application functionality. Consult the NOTES.txt files in
20 each framework's subdirectory of the docs directory for some notes on how
21 applications may be run 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 path information semantics.
38 Fixed file upload semantics.
39 Fixed content type handling for Unicode output and for interpreting request
40 body fields/parameters (although some improvement remains).
41 Fixed field/parameter retrieval so that path and body fields are distinct,
42 regardless of the framework employed.
43 Introduced Zope 2 support.
44 Session support has been added.
45
46 New in WebStack 0.6 (Changes Since WebStack 0.5)
47 ------------------------------------------------
48
49 Introduced Jython/Java Servlet API support.
50 Minor fixes to example applications and to BaseHTTPRequestHandler.
51
52 New in WebStack 0.5 (Changes Since WebStack 0.4)
53 ------------------------------------------------
54
55 Changed request body fields/parameters so that they are now represented using
56 Unicode objects rather than plain strings.
57 Introduced better support for Unicode in response streams.
58
59 New in WebStack 0.4 (Changes Since WebStack 0.3)
60 ------------------------------------------------
61
62 Added application definition of user identity, permitting alternative
63 authentication mechanisms.
64 Improved BaseHTTPRequestHandler and mod_python reliability around fields from
65 request bodies.
66 Provided stream and environment parameterisation in the CGI adapter.
67 Added LoginRedirect and Login examples.
68 Added get_path_without_query and fixed get_path behaviour.
69
70 New in WebStack 0.3 (Changes Since WebStack 0.2)
71 ------------------------------------------------
72
73 Added better header support for Webware (suggested by Ian Bicking).
74 Introduced CGI and Java Servlet support (the latter is currently
75 broken/unfinished).
76 Introduced support for cookies.
77
78 Future Work
79 -----------
80
81 Things to consider for future releases: improved cookie support, redirects,
82 access to shared resources and much better documentation.
83
84 Field access needs testing, especially for anything using the cgi.FieldStorage
85 class, and the way file uploads are exposed should be reviewed (currently the
86 meta-data is not exposed). The acquisition of fields from specific sources
87 should be made more strict - some frameworks (eg. mod_python) provide path
88 fields in the body fields dictionary.
89
90 Cookie objects need defining strictly, especially since the standard library
91 Cookie object behaves differently to mod_python (and possibly Webware) Cookie
92 objects. Moreover, the set_cookie_value method needs to provide access to the
93 usual cookie parameters as supported by the frameworks.
94
95 UTF-16 (and possibly other encodings) causes problems with HTML form data sent
96 in POST requests using the application/x-www-form-urlencoded content type.
97 This should be reviewed at a later date when proper standardisation has taken
98 place.
99
100 Session support, especially through WebStack.Helpers.Session, should be
101 reviewed.
102
103 Release Procedures
104 ------------------
105
106 Update the WebStack/__init__.py __version__ attribute.
107 Update the release notes (see above).
108 Check the setup.py file and ensure that all package directories are mentioned.
109 Tag, export, archive, upload.