Le jeu, 04 f�v 1999, vous avez �crit :
>On Wed, Feb 03, 1999, Khimenko Victor wrote:
>
>> >> Wouldn't it be nice to have EAPI and mod_ssl available as two distincts
>> >> distribs ? So we know when EAPI has been changed and we must rebuild apache
>> >> binary, or when mod_ssl has been changed and we must rebuild mod_ssl DSO.
>>
>> > Hmmm... it would be nice to have a EAPI dist and a mod_ssl dist for the reason
>> > that other module authors could use EAPI without mod_ssl, but not for the
>> > reason you mention IMHO. Actually the rebuilding of DSOs should be no longer
>> > needed, because Apache+EAPI since mod_ssl 2.2.0 can also load standard DSOs.
>> > And OTOH for the "have to dists" issue: You have an EAPI distribution. It's
>> > the same as the mod_ssl distribution but you use --with-eapi-only on the
>> > configure command line. This way only EAPI is applied to the Apache source
>> > tree. Isn't that what you actually want?
>>
>> Looks like you miss his point. It's NOT about OTHER DSO's but about mod_ssl
>> itself. If EAPI and mod_ssl will be separated then with new version of mod_ssl
>> you'll need just recompilation of mod_ssl via apxs but when EAPI is changed
>> you should recompile Apache itself !
>
>Seems like I still miss the point, even after your description. Because you
>already can compile and install just Apache+EAPI with the help of
>"--with-eapi-only" and then when new mod_ssl versions come out just use
>"--with-apxs" to upgrade the mod_ssl part. So, I still don't see the actual
>benefit from having EAPI seperately. The only advantage I already see is that
>other module authors could use EAPI without having to deal with mod_ssl. But
>the upgrade-point you want to address is still not clear to me, sorry. Where
>exactly is the benefit in upgrading? That for Apache+EAPI you have a nicer
>eapi-x.x.tar.gz tarball instead of the mod_ssl tarball?
>
Ralf, I think that Victor and I have to address the same problem.
If we have an eapi-x.x.tar.gz we know that we have to rebuild Apache when it
becomes eapi-x.y.tar.gz.
On the other hand when mod_ssl's version changes we know that we only have to
rebuild mod_ssl.
Do I understand that the eapi is now compatible with standard api and an
Apache+EAPI can run a standard Apache module?
--
Ronan-Yann Lorin tel: +33 603 326 434
Adesium R�seaux & Services mailto:[EMAIL PROTECTED]
France http://www.adesium-services.fr/~lorin
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
