1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
<html>
<head>
<link rel="stylesheet" type="text/css" href="dox.css" />
<title>libapreq2-2.04-dev: libapreq2: STATUS</title>
</head>
<body>
<div id="page-header">
<p class="menu">
<a href="http://www.apache.org/">Apache Software Foundation</a> > <a href="http://httpd.apache.org">HTTP Server Project</a> >
<a href="http://httpd.apache.org/apreq/">Request Library Subproject</a></p>
<p class="apache">Apache HTTP Server Request Library</p>
<img alt="" src="feather.gif" /></div>
<!-- Generated by Doxygen 1.3.8 -->
<div class="qindex"><a class="qindex" href="index.html">Main Page</a> | <a class="qindex" href="modules.html">Modules</a> | <a class="qindex" href="annotated.html">Data Structures</a> | <a class="qindex" href="files.html">File List</a> | <a class="qindex" href="functions.html">Data Fields</a> | <a class="qindex" href="globals.html">Globals</a> | <a class="qindex" href="pages.html">Related Pages</a></div>
<h1><a class="anchor" name="apreq_status">STATUS</a></h1>2.04-dev released on August 30, 2004.<p>
Contributors looking for a mission:<p>
<ul>
<li>just do an egrep on "TODO" or "XXX" and see what's there</li></ul>
<p>
CURRENT RELEASE NOTES:<p>
<ul>
<li>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</li></ul>
<p>
<a href="http://apr.apache.org/versioning.html">http://apr.apache.org/versioning.html</a><p>
do not apply to developer releases.<p>
RELEASE SHOWSTOPPERS:<p>
CURRENT VOTES:<p>
<ul>
<li>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.</li></ul>
<p>
+1: joes 0: -1:<p>
<ul>
<li>We are moving from cvs to subversion as soon as it is convenient. Vote was taken in March 2004 (<a href="http://marc.theaimsgroup.com/?t=107919363000001&r=1&w=2">http://marc.theaimsgroup.com/?t=107919363000001&r=1&w=2</a>) and the results were as follows:</li></ul>
<p>
+1: joes, randyk, stas 0: -1:<p>
TODO:<p>
<ul>
<li>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?</li></ul>
<p>
<ul>
<li>Why must fprintf(stderr, ...), rather than apr_file_printf(err, ...), be used on Win32 in cgi_log() of src/apreq_env.c?</li></ul>
<p>
<ul>
<li>The current tests don't cover these functions, so add CuTest tests for them:<ul>
<li><a class="el" href="apreq_8h.html#a28">apreq_merge_values()</a></li></ul>
</li></ul>
<p>
<ul>
<li>CuTest needs va_arg to print comments for a failed unit test.</li></ul>
<p>
<ul>
<li>Get env/ (Apache::Test) tests to work for --with-apache2-src option.</li></ul>
<p>
<ul>
<li>Bring Perl documentation up to speed: Table.pod, and Error.pod. These docs either need to be written, or they require Test::Inline tests to verify their API.</li></ul>
<p>
<ul>
<li>Write parser/hook API documentation, and add perl glue for the API.</li></ul>
<p>
<ul>
<li>Add XForms logic to the mfd parser.</li></ul>
<p>
<ul>
<li>symbol exports files:<ol>
<li>aix needs .exp files</li></ol>
</li></ul>
<p>
<ul>
<li>Install the html dox during "make install". Should we do this for the doxy manpages also?</li></ul>
<p>
<ul>
<li>Rework glue/perl build system to use apreq2-config instead of relying on paths like "../../src".</li></ul>
<p>
<ul>
<li>Taint checks need to be extended to APR objects, like $upload->bb and $upload->info. We may need be able to do that with additional typemaps.</li></ul>
<p>
OPEN ISSUES:<p>
<ul>
<li>Should we bundle an apr-based "application/xml" parser? If so, how should we parse the xml data into an apr_table?</li></ul>
<p>
BUGS:<p>
<ul>
<li>Fix build automake/libtool/autoconf build system so it works properly on OSX & AIX.</li></ul>
<p>
WISH LIST:<p>
<ul>
<li>I [joes] wish folks would contribute some glue code for one of these:</li></ul>
<p>
<ul>
<li>php,</li><li>Rivet,</li><li>mod_dtcl,</li><li>mod_python,</li><li>mod_jk,</li><li>tomcat,</li><li>mod_ruby,</li><li>mod_parrot. </li></ul>
<div id="footer">
<p class="apache">
Copyright © 2003-2004 <a href="http://www.apache.org">The Apache Software Foundation</a>.<br/>
See <a href="LICENSE.html">LICENSE</a>.</p>
<p class="menu">
<span style="color:#aaa">page generated by <a href="http://www.doxygen.org/"><code>doxygen</code></a>
version 1.3.8 on 30 Aug 2004</span>
</p>
</div>
</body>
</html>
|
