1.1 --- a/README.txt Thu Aug 25 22:47:52 2005 +0000
1.2 +++ b/README.txt Fri Aug 26 01:27:37 2005 +0000
1.3 @@ -59,6 +59,8 @@
1.4 get_virtual_path_info, get_processed_virtual_path_info and
1.5 get_fields_from_path to return Unicode data decoded using the optional
1.6 encoding parameter or a common default encoding.
1.7 +Fixed file upload values so that plain strings are returned for such fields in
1.8 +get_fields_from_body and get_fields. (Warning! Except for Twisted!)
1.9 Updated/fixed LoginResource and LoginRedirectResource to use the updated path
1.10 API and to handle special characters properly.
1.11 Added convenience methods to Transaction for the decoding and encoding of path
1.12 @@ -178,6 +180,12 @@
1.13
1.14 (Essential)
1.15
1.16 +Twisted 1.3.0 does not provide file upload metadata, and Twisted Web 0.5.0
1.17 +also seems to be missing this functionality. It isn't obvious whether Twisted
1.18 +Web2 will just copy its predecessors and provide a similarly limited API.
1.19 +Perhaps the Twisted support needs to resemble the CGI support much more when
1.20 +handling fields.
1.21 +
1.22 JythonServlet libraries need to be configured using sys.add_package when
1.23 these do not feature in the compiled-in list. Adding such configuration to
1.24 the handler may be most appropriate (since the web.xml file can be too
1.25 @@ -199,7 +207,9 @@
1.26 stray path fields are handled (eg. in WebStack.Helpers.Request) as being
1.27 ISO-8859-1, but it might be the case that some such fields might be
1.28 submitted as UTF-8. The decode_path method on Transaction does do much of the
1.29 -work that is likely to be required, however.
1.30 +work that is likely to be required, however. Still, a good policy for decoding
1.31 +path fields, reducing the number of times one might specify the encoding in
1.32 +various method calls, may be important.
1.33
1.34 An interesting test of encodings is to introduce things like the following to
1.35 the path info and query string sections of the URL: %25F0?%E6=%F8&%25F0=%F8
1.36 @@ -225,9 +235,6 @@
1.37 HeaderValue objects should be employed more extensively. Thus, the header
1.38 access methods may need to change their behaviour slightly.
1.39
1.40 -Investigate the nicer functions in the cgi module, discarding the "magic"
1.41 -stuff like FieldStorage.
1.42 -
1.43 WSGI support could demand that a special "end of headers" method be
1.44 introduced into WebStack, thus making response output more efficient (and
1.45 probably also for other frameworks, too).
1.46 @@ -239,6 +246,8 @@
1.47
1.48 Consider packages for different operating systems (other than Debian).
1.49
1.50 +Provide some 500 error content when handle_errors is true.
1.51 +
1.52 (Completed/rejected)
1.53
1.54 The location of deployed applications in the filesystem should be exposed to
1.55 @@ -248,6 +257,11 @@
1.56 Path information should be consistent across all frameworks, and the "path
1.57 info" value should be meaningful. (This should now be correct.)
1.58
1.59 +Investigate the nicer functions in the cgi module, discarding the "magic"
1.60 +stuff like FieldStorage. (These nicer functions are used by projects like
1.61 +Twisted - as of 1.3.0 at least - and do not give the necessary information we
1.62 +require.)
1.63 +
1.64 Release Procedures
1.65 ------------------
1.66