httpd-apreq-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject cvs commit: httpd-apreq-2 STATUS
Date Fri, 13 Jun 2003 01:01:37 GMT
joes        2003/06/12 18:01:37

  Modified:    .        STATUS
  Log:
  STATUS update & cleanup.
  
  Revision  Changes    Path
  1.10      +38 -36    httpd-apreq-2/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/httpd-apreq-2/STATUS,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- STATUS	12 Jun 2003 06:08:53 -0000	1.9
  +++ STATUS	13 Jun 2003 01:01:36 -0000	1.10
  @@ -38,44 +38,51 @@
   
   TODO:
   
  +    * Settle on the Perl API and start tracking CHANGES.
  +
       * Add documentation system.
   
         [joes] suggests:
   
  -      * doxygen for C API (header comments).
  -
  -      * perldoc for Perl glue (pod).
  +      - doxygen for C API (header comments).
  +      - perldoc for Perl glue (pod).
       
   
       * Populate the glue/ directory.
   
  -      * Port apreq-1's Apache::Test tests for the Perl API into glue/perl/t.
  -
  -      * ExtUtils::XSBuilder framework for glue/perl is in place.
  +      - Improve test suite to ensure all glue/perl/t tests pass.
  +      - ExtUtils::XSBuilder framework for glue/perl is in place.
           Now perl developers should be able to build & compile
  -        Request.xs & Cookie.xs.  The Apache::Test tests from apreq-1
  -        are really needed now to establish the API, and make it
  -        play nice with (& without) modperl-2.
  +        Request.xs & Cookie.xs.
   
       * Add XForms logic to the mfd parser.
   
  -  * symbol exports files:
  -    - win32 now has hardcoded .def files (need to automate, e.g. based
  -      on exports.c ala httpd-2.0)
  -    - aix needs .exp files
  -
  -  * on Win32, figure out how to build things so Apache::Cookie
  -    and Apache::Request don't need to be linked against mod_apreq
  -    to resolve missing apreq_env* symbols. 
  +    * symbol exports files:
  +      - win32 now has hardcoded .def files (need to automate, e.g. based
  +        on exports.c ala httpd-2.0)
  +      - aix needs .exp files
  +
  +    * on Win32, figure out how to build things so Apache::Cookie
  +      and Apache::Request don't need to be linked against mod_apreq
  +      to resolve missing apreq_env* symbols. 
  +
  +    * perl ../build/test_config.pl -apxs ...  
  +      ignores the command-line (apxs) arguments on some platforms.
  +      This prevents the env/ tests from building on those systems.
   
   
   OPEN ISSUES:
   
  -  Documentation system.
  +    * Documentation system.
   
  -  Should we bundle an apr-based "application/xml" parser?  
  -  If so, how should we parse the xml data into an apr_table?
  +    * Should we bundle an apr-based "application/xml" parser?  
  +      If so, how should we parse the xml data into an apr_table?
   
  +    * How should the Perl API work in a CGI context?
  +      Will users need to preload an "CGI environment" module 
  +      before loading Request.so or Cookie.so?
  +
  +    * Figure out how to bundle a CPAN release.
   
   BUGS:
   
  @@ -84,20 +91,15 @@
   
   WISH LIST:
   
  -     [joes] I wish folks would contribute some glue code for
  -     one of these:
  -
  -              php, 
  -
  -              mod_tcl, 
  -
  -              mod_python, 
  -
  -              mod_jk, 
  -
  -              mod_ruby,
  +    * I [joes] wish folks would contribute some glue code for
  +      one of these:
   
  -              mod_parrot.
  +      - php, 
  +      - mod_tcl, 
  +      - mod_python, 
  +      - mod_jk, 
  +      - mod_ruby,
  +      - mod_parrot.
   
  -     Someone should also adopt env/libapreq_cgi.c and ensure it
  -     donesn't fall into disrepair by adding some tests for it to env/t.
  +    * Someone should also adopt env/libapreq_cgi.c and ensure it
  +      doesn't fall into disrepair by adding some tests to env/t.
  
  
  

Mime
View raw message