Re: APR's thread-detection heuristics

["Roy T. Fielding" <fi...@kiwi.ICS.UCI.EDU>]

>> Things like platforms.m4 and threads.m4 should be kept in APR.
>
>That works for now, but there are things that Apache may require,
>as far as pre-loading, seperate from APR which would require
>it's own platforms.m4-type file. So we may be "overloading"
>platforms.m4 beyond what is "just" meant for APR.

My opinion is that all configuration platform issues for Apache should be
handled in APR, whether or not APR code requires it.  httpd should
only have to use what APR generates.

....Roy

Re: APR's thread-detection heuristics

[rb...@covalent.net]

> >That works for now, but there are things that Apache may require,
> >as far as pre-loading, seperate from APR which would require
> >it's own platforms.m4-type file. So we may be "overloading"
> >platforms.m4 beyond what is "just" meant for APR.
> 
> My opinion is that all configuration platform issues for Apache should be
> handled in APR, whether or not APR code requires it.  httpd should
> only have to use what APR generates.

I'm not quite agreeing with you 100%, but I definately agree
95-99%.  :-)  Right now, we do a lot of checks in both places.  This is
stupid.  Apache should just be using what APR defines, and the Apache
configure script should be minimal.

Ryan

_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------