Main Page Modules Data Structures File List Data Fields Globals Related Pages
2.03-dev released June 12, 2004
Contributors looking for a mission:
- just do an egrep on "TODO" or "XXX" and see what's there
CURRENT RELEASE NOTES:
- This is a developer release, indicated by the "-dev" suffix on the version string. We believe the core interfaces to be stable, but some portions of the API may still need significant modification. Thus, binary/source compatibility may be broken from one developer release to the next. In particular the version numbering rules specified at
http://apr.apache.org/versioning.html
do not apply to developer releases.
RELEASE SHOWSTOPPERS:
CURRENT VOTES:
- Should we switch to EU::MM for determining the full path to perl? The problem is that some folks move their perl binary post-installation, but never adjust Config.pm. EU::MM is smart, by accepting a full path in $^X or by searching the user's $PATH for $^X, before resorting to Config.pm. However, if we change apreq2, we should also lobby test-dev to adopt the same solution for Apache::Test. Otherwise our test suite will likely fail, even though the rest of the perl build system will presumably still work.
+1: joes 0: -1:
- Should we replace req->body with an iterator API (added to apreq_parser_t)? The rationale is that this would make xml parsing possible (xml data doesn't map naturally to apr_table_t). Xml support is a requirement for XForms. The disadvantage is that there may be a performance hit due to the additional abstractions.
+1: joes 0: -1:
+1: joes, randyk, stas 0: -1:
TODO:
- Include perl glue for CGI environment.
- Get env/ (Apache::Test) tests to work for --with-apache2-src option.
- Bring Perl documentation up to speed.
- Write parser/hook API documentation.
- Add XForms logic to the mfd parser.
- symbol exports files:
- aix needs .exp files
OPEN ISSUES:
- Should we bundle an apr-based "application/xml" parser? If so, how should we parse the xml data into an apr_table?
BUGS:
- Fix build automake/libtool/autoconf build system so it works properly on OSX & AIX.
- The current API does not handle failed query_string parsing adequately (apreq_request does log an error message, but there's no status code in the struct for users to interrogate).
WISH LIST:
- I [joes] wish folks would contribute some glue code for one of these:
- php,
- Rivet,
- mod_dtcl,
- mod_python,
- mod_jk,
- tomcat,
- mod_ruby,
- mod_parrot.
Generated on Sat Jun 12 10:16:30 2004 for libapreq2 by
1.2.15