dgaudet     98/03/12 03:30:08

  Modified:    .        STATUS
  Log:
  el nino is taking a break, we've had sun for several days... p.s. something 
to vote on
  
  Revision  Changes    Path
  1.184     +18 -36    apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.183
  retrieving revision 1.184
  diff -u -r1.183 -r1.184
  --- STATUS    1998/03/10 08:52:55     1.183
  +++ STATUS    1998/03/12 11:30:07     1.184
  @@ -226,6 +226,24 @@
         explicitly names the variant selected.  Should it do so, or should
         the base input name be referenced?
   
  +    * Proposed API Changes:
  +
  +     - r->content_language is for backwards compatibility... with modules
  +       that may not link any longer without some minor editing.  The new
  +       field is r->content_languages.  Heck it's not even mentioned in
  +       apache-devsite/mmn.txt when we got content_languages (note the s!).
  +       The proposal is to remove r->content_language:
  +         Status: Dean +1
  +
  +     - child_exit() is redundant, it can be implemented via cleanups.  It is
  +       not "symmetric" in the sense that there is no exit API method to go
  +       along with the init() API method.  There is no need for an exit
  +       method, there are already modules using cleanups to perform this (see
  +       mod_mmap_static, and mod_php3 for example).  The proposal is to
  +       remove the child_exit() method and document cleanups as the method of
  +       handling this need.
  +         Status: Dean +1, Rasmus +1
  +
   Win32 specific issues:
   
    Open issues:
  @@ -347,39 +365,3 @@
       * SECURITY: numerous uses of strcpy and strcat have potential
        for buffer overflow, someone should rewrite or verify
        they're safe
  -
  -Proposed announcement for -testers mailing list:
  -
  -    The Apache Group would like to expand the audience that is available
  -    for testing during the development cycles.  In particular, the stable
  -    release (1.2 currently) receives less testing by the developers
  -    because the developers are generally running the development release
  -    (1.3 currently).  To aid this we have created two mailing lists:
  -    stable-testers and current-testers.
  -
  -    Volunteers willing to test drive versions of the stable branch of
  -    the Apache HTTP Server should send a message to [EMAIL PROTECTED]
  -    containing the words:
  -
  -     subscribe stable-testers
  -
  -    Volunteers willing to test drive versions of the current development
  -    branch of the Apache HTTP Server should send a message to
  -    [EMAIL PROTECTED] containing the words:
  -
  -     subscribe current-testers
  -
  -    These forums will be predominantly one-way: when the Apache Group has
  -    a new release ready, they will let the appropriate list know about it
  -    first, and then it is *expected* that people will pull it down from
  -    the Apache web site (or one of its mirrors) and give it a spin.  If
  -    you see a problem, and have with due diligence verified that it
  -    isn't a configuration error, and it's definitely a difference in
  -    behavior from the last public release in the series, then please
  -    post here about it.
  -
  -    Thanks!
  -
  -    Dean intends to post this on friday, around noon PST.
  -
  -    Status: Dean +1, Ken +1, Ralf +1, Martin +1
  
  
  

Reply via email to