# HG changeset patch
# User paulb
# Date 1094506199 0
# Node ID 861474231d554b6ea8e80eb1fa57262a58e6398b
# Parent  3f1180831cf8363c36ab37061c1dfdb185d1d6c1
[project @ 2004-09-06 21:29:59 by paulb]
Added more notes on the current status of the software.

diff -r 3f1180831cf8 -r 861474231d55 README.txt
--- a/README.txt	Sun Sep 05 17:59:38 2004 +0000
+++ b/README.txt	Mon Sep 06 21:29:59 2004 +0000
@@ -87,8 +87,13 @@
 Field access needs testing, especially for anything using the cgi.FieldStorage
 class, and the way file uploads are exposed should be reviewed (currently the
 meta-data is not exposed). The acquisition of fields from specific sources
-should be made more strict - some frameworks (eg. mod_python) provide path
-fields in the body fields dictionary.
+should be tested with different request methods - some frameworks provide path
+fields in the body fields dictionary, others (eg. Zope) change the fields
+exposed depending on request method.
+
+Interpretation of path field encodings needs to be verified. Currently, stray
+path fields are handled (eg. in WebStack.Helpers.Request) as being ISO-8859-1,
+but it might be the case that some such fields might be submitted as UTF-8.
 
 Cookie objects need defining strictly, especially since the standard library
 Cookie object behaves differently to mod_python (and possibly Webware) Cookie
@@ -101,7 +106,16 @@
 place.
 
 Session support, especially through WebStack.Helpers.Session, should be
-reviewed.
+reviewed and be made compatible with non-cookie mechanisms.
+
+The location of deployed applications in the filesystem should be exposed to
+those applications.
+
+HeaderValue objects should be employed more extensively. Thus, the header
+access methods may need to change their behaviour slightly.
+
+Investigate the nicer functions in the cgi module, discarding the "magic"
+stuff like FieldStorage.
 
 Release Procedures
 ------------------