Author: joes
Date: Wed Oct 12 13:24:48 2005
New Revision: 315030
URL: http://svn.apache.org/viewcvs?rev=315030&view=rev
Log:
Drop obvious API breaking issues/todos,
promote RFC-2047 issue to showstopper for now.
Modified:
httpd/apreq/trunk/STATUS
Modified: httpd/apreq/trunk/STATUS
URL:
http://svn.apache.org/viewcvs/httpd/apreq/trunk/STATUS?rev=315030&r1=315029&r2=315030&view=diff
==============================================================================
--- httpd/apreq/trunk/STATUS (original)
+++ httpd/apreq/trunk/STATUS Wed Oct 12 13:24:48 2005
@@ -13,6 +13,7 @@
RELEASE SHOWSTOPPERS:
- The perl docs are missing Test::Inline tests.
+ - Implement (some of) RFC 2047 in the multipart parser.
CURRENT VOTES:
@@ -33,8 +34,6 @@
TODO:
- - Implement (some of) RFC 2047 in the multipart parser.
-
- Dump automake, preferably replacing that with more stuff from
httpd/apr's build system.
@@ -58,12 +57,6 @@
error status should be both tested & documented. Also
upgrade these tests to use the Apache::Test framework.
- - Add a "memory_limit" setting to apreq_parser_t and apreq_module_t,
- which will control how much pool allocation the parser may use.
-
- - Add a "header_limit" setting to control outgoing header size
- (mainly for baking cookies) instead of using a compiled-in limit.
-
- in glue/perl/t/apreq/cgi.t on Win32, printing to the error log
hangs if the strings involved are about 10000 in size.
This doesn't occur in the env/cgi tests - why?
@@ -90,14 +83,6 @@
- Should we bundle an apr-based "application/xml" parser?
If so, how should we parse the xml data into an apr_table?
-
- - Determine whether or not it's good for the perl glue to ever set
- the SvUTF8 flag on a param. The current code ties this action to the
- apreq_param_is_tainted flag.
-
- - Should we let hooks interrupt parsers via APREQ_ERROR_INTERRUPT?
- That'd need a delete_hook method to make interrupts a useful
- way of tuning parser behavior.
BUGS:
