You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@hyperreal.org on 1999/07/07 13:05:16 UTC

cvs commit: apache-1.3 STATUS

coar        99/07/07 04:05:16

  Modified:    .        STATUS
  Log:
  	Veto EAPI for 1.3.7 (too much confusion and controversy, esp.
  	with the KEAPI alternative); defer it until the next release.
  	Also note some platforms I can build.
  
  Revision  Changes    Path
  1.724     +8 -30     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.723
  retrieving revision 1.724
  diff -u -r1.723 -r1.724
  --- STATUS	1999/06/25 08:12:18	1.723
  +++ STATUS	1999/07/07 11:05:15	1.724
  @@ -1,9 +1,11 @@
     1.3 STATUS:
  -  Last modified at [$Date: 1999/06/25 08:12:18 $]
  +  Last modified at [$Date: 1999/07/07 11:05:15 $]
   
   Release:
   
       1.3.7-dev: current.  Ken volunteers to be release manager.
  +        Proposed dates: roll on Mon, 26 July 1999, test, and release
  +        on Fri, 30 July 1999.
   
       1.3.6. Tagged and rolled on Mar. 22. Released and announced on 24th.
       1.3.5: Not released.
  @@ -20,7 +22,7 @@
    Platform                      Avail.  Volunteer
    ------------------------------------------------------------------------------
    alpha-dec-osf3.0              no      Sameer Parekh
  - alpha-dec-osf4.0              yes     Lars Eilebrecht
  + alpha-dec-osf4.0              yes     Lars Eilebrecht, Ken Coar
    armv4l-whatever-linux2        yes     Rasmus Lerdorf
    hppa1.1-hp-hpux               no      Rob Hartill
    i386-slackware-linux(a.out)   no      Sameer Parekh
  @@ -34,9 +36,10 @@
    i686-pc-freebsd3.1            no      Ralf S. Engelschall
    i586-unknown-linux2           yes     Ralf S. Engelschall, Lars Eilebrecht
    i686-unknown-linux2           yes     Lars Eilebrecht
  + i686-whatever-linux2          yes     Ken Coar
    i386-unknown-linux(ELF)       no      Aram Mirzadeh, Michael Douglass
    i386-unknown-netBSD-1.2.1     N/A     Lars Eilebrecht
  - i386-unknown-netBSD-1.3.2     yes      Lars Eilebrecht
  + i386-unknown-netBSD-1.3.2     yes     Lars Eilebrecht
    i386-unknown-sco3             no      Ben Laurie
    i386-unknown-sco5             no      Ben Laurie
    i386-sni-svr4                 yes     Martin Kraemer
  @@ -105,33 +108,8 @@
   	Status: Jim +1, Mark +1, Dean +1, BenH +1,
   		Randy +1 (please choose name other than "hook")
                   Doug +1 on concept (untested), Lars +1 on concept,
  -		Martin +1 (untested),
  -
  -		Ken: -1 for pre-2.0 if it will: a) force a new release of
  -		mod_perl or mod_php in order to maintain compatibility OR
  -		b) require a version bump to 1.4.0 and a beta cycle
  -                Ralf: It doesn't force a new release of any module (just a
  -                recompilation), because it's a pure _ADDITION_ to the API and
  -                doesn't make anything incompatible. The point b) I still do
  -                not sunderstand, sorry. 
  -
  -                * Hmmmm.... now we've to solve another problem for the EAPI
  -                * idea: the existance of KEAPI. That's not my problem any
  -                * longer.  Others have to make decisions now. Additionally the
  -                * group as a whole is far away from a point where it's clear
  -                * what should be done in the future and also far away from
  -                * the point where it's fun. 
  -                *
  -                * So I finally withdraw my proposed addition of EAPI for
  -                * 1.3.7/1.4.0 and for 2.0 I've still no strong opinion how it
  -                * should be done.  I'll try to stay out of all this and keep
  -                * being happy to have EAPI myself and don't have to worry
  -                * about all those useless politics and endless ping-pong
  -                * decisions.
  -                *
  -                * IMHO the ASF should really quickly propose the
  -                * revitalization of RST's old ENOTOWN symbolic errno value 
  -                * for use by its developers...       -- RSE
  +		Martin +1 (untested), Ken -1 for 1.3.7 (too controversial,
  +		esp. w/KEAPI offered as well)
   
       * Brian Havard's patch to remove dependency of mod_auth_dbm on mod_auth.
         (PR#2598)
  
  
  

Re: cvs commit: apache-1.3 STATUS

Posted by Ben Laurie <be...@algroup.co.uk>.
Michael H. Voase wrote:
> 
> Ben Laurie wrote:
> >
> > coar@hyperreal.org wrote:
> 
> > I invite interested parties to look at what I'm doing in MPM before its
> > too late.
> >
> 
>         Ben , where is it dude ? I have scratched around your site ,
> its references , your id page and anything else I can scratch up
> all to no avail ...
> 
> Wanna provide a link to this or is this internal to the ASF ?

Its in the Apache 2.0 CVS tree, in the mpm directory.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

Re: cvs commit: apache-1.3 STATUS

Posted by "Michael H. Voase" <mv...@midcoast.com.au>.
Ben Laurie wrote:
> 
> coar@hyperreal.org wrote:
 
> I invite interested parties to look at what I'm doing in MPM before its
> too late.
> 

	Ben , where is it dude ? I have scratched around your site ,
its references , your id page and anything else I can scratch up
all to no avail ...

Wanna provide a link to this or is this internal to the ASF ?

Cheers Mik Voase.

> BTW, the implementation of these hooks currently uses the preprocessor,
> which is rapidly getting ugly. I'm strongly considering writing a custom
> hook compiler to keep things readable, so please don't criticise on the
> grounds that you don't like the preprocesser messiness.
> 
> Cheers,
> 
> Ben.
> 
> --
> http://www.apache-ssl.org/ben.html
> 
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
>      - Indira Gandhi

-- 
----------------------------------------------------------------------------
 /~\     /~\            CASTLE INDUSTRIES PTY. LTD.
 | |_____| |            Incorporated 1969. in N.S.W., Australia
 |         |            Phone +612 6567 1227 Fax +612 6567 1449
 |   /~\   |            Web http://www.midcoast.com.au/~mvoase
 |   [ ]   |            Michael H. Voase.  Director.
~~~~~~~~~~~~~~          Castle Industries - Industrial Strength
Solutions.
----------------------------------------------------------------------------

Re: cvs commit: apache-1.3 STATUS

Posted by Ben Laurie <be...@algroup.co.uk>.
coar@hyperreal.org wrote:
> 
> coar        99/07/07 04:05:16
> 
>   Modified:    .        STATUS
>   Log:
>         Veto EAPI for 1.3.7 (too much confusion and controversy, esp.
>         with the KEAPI alternative); defer it until the next release.
>         Also note some platforms I can build.

Note that I am introducing further confusion by replacing the entire
module callback API with hooks in MPM.

There are various reasons I haven't used either EAPI or KEAPI but here's
the highlights:

a) efficiency
b) 100% typesafeness
c) entanglement with SSL (in at least KEAPI's case)
d) somewhat different motivation: I want to replace the whole callback
API and allow protocol independence
e) I need a way to allow modules to specify ordering, which (AFAIK)
neither EAPI or KEAPI had
f) The first great virtue of a programmer, laziness: as has been
observed, writing the hooking stuff isn't that hard. It was easier for
me to start again than to figure out how to hack things to get where I
want to go.
g) I was kind of hoping that people might contribute if I do it a piece
at a time, thus getting something everyone is happy with.

It is my opinion that extending the API in 1.3.x is a pointless
distraction of effort.

I invite interested parties to look at what I'm doing in MPM before its
too late.

BTW, the implementation of these hooks currently uses the preprocessor,
which is rapidly getting ugly. I'm strongly considering writing a custom
hook compiler to keep things readable, so please don't criticise on the
grounds that you don't like the preprocesser messiness.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

Re: cvs commit: apache-1.3 STATUS

Posted by Ben Laurie <be...@algroup.co.uk>.
coar@hyperreal.org wrote:
> 
> coar        99/07/07 04:05:16
> 
>   Modified:    .        STATUS
>   Log:
>         Veto EAPI for 1.3.7 (too much confusion and controversy, esp.
>         with the KEAPI alternative); defer it until the next release.
>         Also note some platforms I can build.

Note that I am introducing further confusion by replacing the entire
module callback API with hooks in MPM.

There are various reasons I haven't used either EAPI or KEAPI but here's
the highlights:

a) efficiency
b) 100% typesafeness
c) entanglement with SSL (in at least KEAPI's case)
d) somewhat different motivation: I want to replace the whole callback
API and allow protocol independence
e) I need a way to allow modules to specify ordering, which (AFAIK)
neither EAPI or KEAPI had
f) The first great virtue of a programmer, laziness: as has been
observed, writing the hooking stuff isn't that hard. It was easier for
me to start again than to figure out how to hack things to get where I
want to go.
g) I was kind of hoping that people might contribute if I do it a piece
at a time, thus getting something everyone is happy with.

It is my opinion that extending the API in 1.3.x is a pointless
distraction of effort.

I invite interested parties to look at what I'm doing in MPM before its
too late.

BTW, the implementation of these hooks currently uses the preprocessor,
which is rapidly getting ugly. I'm strongly considering writing a custom
hook compiler to keep things readable, so please don't criticise on the
grounds that you don't like the preprocesser messiness.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

Re: cvs commit: apache-1.3 STATUS

Posted by Dirk-Willem van Gulik <di...@webweaving.org>.
	Did anyone else test the IPv6 patch ? Preferably
	on non solaris / non freebsd ?

Dw.

On 7 Jul 1999 coar@hyperreal.org wrote:

> coar        99/07/07 04:05:16
> 
>   Modified:    .        STATUS
>   Log:
>   	Veto EAPI for 1.3.7 (too much confusion and controversy, esp.
>   	with the KEAPI alternative); defer it until the next release.
>   	Also note some platforms I can build.
>   
>   Revision  Changes    Path
>   1.724     +8 -30     apache-1.3/STATUS
>   
>   Index: STATUS
>   ===================================================================
>   RCS file: /home/cvs/apache-1.3/STATUS,v
>   retrieving revision 1.723
>   retrieving revision 1.724
>   diff -u -r1.723 -r1.724
>   --- STATUS	1999/06/25 08:12:18	1.723
>   +++ STATUS	1999/07/07 11:05:15	1.724
>   @@ -1,9 +1,11 @@
>      1.3 STATUS:
>   -  Last modified at [$Date: 1999/06/25 08:12:18 $]
>   +  Last modified at [$Date: 1999/07/07 11:05:15 $]
>    
>    Release:
>    
>        1.3.7-dev: current.  Ken volunteers to be release manager.
>   +        Proposed dates: roll on Mon, 26 July 1999, test, and release
>   +        on Fri, 30 July 1999.
>    
>        1.3.6. Tagged and rolled on Mar. 22. Released and announced on 24th.
>        1.3.5: Not released.
>   @@ -20,7 +22,7 @@
>     Platform                      Avail.  Volunteer
>     ------------------------------------------------------------------------------
>     alpha-dec-osf3.0              no      Sameer Parekh
>   - alpha-dec-osf4.0              yes     Lars Eilebrecht
>   + alpha-dec-osf4.0              yes     Lars Eilebrecht, Ken Coar
>     armv4l-whatever-linux2        yes     Rasmus Lerdorf
>     hppa1.1-hp-hpux               no      Rob Hartill
>     i386-slackware-linux(a.out)   no      Sameer Parekh
>   @@ -34,9 +36,10 @@
>     i686-pc-freebsd3.1            no      Ralf S. Engelschall
>     i586-unknown-linux2           yes     Ralf S. Engelschall, Lars Eilebrecht
>     i686-unknown-linux2           yes     Lars Eilebrecht
>   + i686-whatever-linux2          yes     Ken Coar
>     i386-unknown-linux(ELF)       no      Aram Mirzadeh, Michael Douglass
>     i386-unknown-netBSD-1.2.1     N/A     Lars Eilebrecht
>   - i386-unknown-netBSD-1.3.2     yes      Lars Eilebrecht
>   + i386-unknown-netBSD-1.3.2     yes     Lars Eilebrecht
>     i386-unknown-sco3             no      Ben Laurie
>     i386-unknown-sco5             no      Ben Laurie
>     i386-sni-svr4                 yes     Martin Kraemer
>   @@ -105,33 +108,8 @@
>    	Status: Jim +1, Mark +1, Dean +1, BenH +1,
>    		Randy +1 (please choose name other than "hook")
>                    Doug +1 on concept (untested), Lars +1 on concept,
>   -		Martin +1 (untested),
>   -
>   -		Ken: -1 for pre-2.0 if it will: a) force a new release of
>   -		mod_perl or mod_php in order to maintain compatibility OR
>   -		b) require a version bump to 1.4.0 and a beta cycle
>   -                Ralf: It doesn't force a new release of any module (just a
>   -                recompilation), because it's a pure _ADDITION_ to the API and
>   -                doesn't make anything incompatible. The point b) I still do
>   -                not sunderstand, sorry. 
>   -
>   -                * Hmmmm.... now we've to solve another problem for the EAPI
>   -                * idea: the existance of KEAPI. That's not my problem any
>   -                * longer.  Others have to make decisions now. Additionally the
>   -                * group as a whole is far away from a point where it's clear
>   -                * what should be done in the future and also far away from
>   -                * the point where it's fun. 
>   -                *
>   -                * So I finally withdraw my proposed addition of EAPI for
>   -                * 1.3.7/1.4.0 and for 2.0 I've still no strong opinion how it
>   -                * should be done.  I'll try to stay out of all this and keep
>   -                * being happy to have EAPI myself and don't have to worry
>   -                * about all those useless politics and endless ping-pong
>   -                * decisions.
>   -                *
>   -                * IMHO the ASF should really quickly propose the
>   -                * revitalization of RST's old ENOTOWN symbolic errno value 
>   -                * for use by its developers...       -- RSE
>   +		Martin +1 (untested), Ken -1 for 1.3.7 (too controversial,
>   +		esp. w/KEAPI offered as well)
>    
>        * Brian Havard's patch to remove dependency of mod_auth_dbm on mod_auth.
>          (PR#2598)
>   
>   
>   
> 


Re: cvs commit: apache-1.3 STATUS

Posted by Dirk-Willem van Gulik <di...@webweaving.org>.
	Did anyone else test the IPv6 patch ? Preferably
	on non solaris / non freebsd ?

Dw.

On 7 Jul 1999 coar@hyperreal.org wrote:

> coar        99/07/07 04:05:16
> 
>   Modified:    .        STATUS
>   Log:
>   	Veto EAPI for 1.3.7 (too much confusion and controversy, esp.
>   	with the KEAPI alternative); defer it until the next release.
>   	Also note some platforms I can build.
>   
>   Revision  Changes    Path
>   1.724     +8 -30     apache-1.3/STATUS
>   
>   Index: STATUS
>   ===================================================================
>   RCS file: /home/cvs/apache-1.3/STATUS,v
>   retrieving revision 1.723
>   retrieving revision 1.724
>   diff -u -r1.723 -r1.724
>   --- STATUS	1999/06/25 08:12:18	1.723
>   +++ STATUS	1999/07/07 11:05:15	1.724
>   @@ -1,9 +1,11 @@
>      1.3 STATUS:
>   -  Last modified at [$Date: 1999/06/25 08:12:18 $]
>   +  Last modified at [$Date: 1999/07/07 11:05:15 $]
>    
>    Release:
>    
>        1.3.7-dev: current.  Ken volunteers to be release manager.
>   +        Proposed dates: roll on Mon, 26 July 1999, test, and release
>   +        on Fri, 30 July 1999.
>    
>        1.3.6. Tagged and rolled on Mar. 22. Released and announced on 24th.
>        1.3.5: Not released.
>   @@ -20,7 +22,7 @@
>     Platform                      Avail.  Volunteer
>     ------------------------------------------------------------------------------
>     alpha-dec-osf3.0              no      Sameer Parekh
>   - alpha-dec-osf4.0              yes     Lars Eilebrecht
>   + alpha-dec-osf4.0              yes     Lars Eilebrecht, Ken Coar
>     armv4l-whatever-linux2        yes     Rasmus Lerdorf
>     hppa1.1-hp-hpux               no      Rob Hartill
>     i386-slackware-linux(a.out)   no      Sameer Parekh
>   @@ -34,9 +36,10 @@
>     i686-pc-freebsd3.1            no      Ralf S. Engelschall
>     i586-unknown-linux2           yes     Ralf S. Engelschall, Lars Eilebrecht
>     i686-unknown-linux2           yes     Lars Eilebrecht
>   + i686-whatever-linux2          yes     Ken Coar
>     i386-unknown-linux(ELF)       no      Aram Mirzadeh, Michael Douglass
>     i386-unknown-netBSD-1.2.1     N/A     Lars Eilebrecht
>   - i386-unknown-netBSD-1.3.2     yes      Lars Eilebrecht
>   + i386-unknown-netBSD-1.3.2     yes     Lars Eilebrecht
>     i386-unknown-sco3             no      Ben Laurie
>     i386-unknown-sco5             no      Ben Laurie
>     i386-sni-svr4                 yes     Martin Kraemer
>   @@ -105,33 +108,8 @@
>    	Status: Jim +1, Mark +1, Dean +1, BenH +1,
>    		Randy +1 (please choose name other than "hook")
>                    Doug +1 on concept (untested), Lars +1 on concept,
>   -		Martin +1 (untested),
>   -
>   -		Ken: -1 for pre-2.0 if it will: a) force a new release of
>   -		mod_perl or mod_php in order to maintain compatibility OR
>   -		b) require a version bump to 1.4.0 and a beta cycle
>   -                Ralf: It doesn't force a new release of any module (just a
>   -                recompilation), because it's a pure _ADDITION_ to the API and
>   -                doesn't make anything incompatible. The point b) I still do
>   -                not sunderstand, sorry. 
>   -
>   -                * Hmmmm.... now we've to solve another problem for the EAPI
>   -                * idea: the existance of KEAPI. That's not my problem any
>   -                * longer.  Others have to make decisions now. Additionally the
>   -                * group as a whole is far away from a point where it's clear
>   -                * what should be done in the future and also far away from
>   -                * the point where it's fun. 
>   -                *
>   -                * So I finally withdraw my proposed addition of EAPI for
>   -                * 1.3.7/1.4.0 and for 2.0 I've still no strong opinion how it
>   -                * should be done.  I'll try to stay out of all this and keep
>   -                * being happy to have EAPI myself and don't have to worry
>   -                * about all those useless politics and endless ping-pong
>   -                * decisions.
>   -                *
>   -                * IMHO the ASF should really quickly propose the
>   -                * revitalization of RST's old ENOTOWN symbolic errno value 
>   -                * for use by its developers...       -- RSE
>   +		Martin +1 (untested), Ken -1 for 1.3.7 (too controversial,
>   +		esp. w/KEAPI offered as well)
>    
>        * Brian Havard's patch to remove dependency of mod_auth_dbm on mod_auth.
>          (PR#2598)
>   
>   
>   
>