>> what can happen if I load a module compiled with EAPI flag into a Apache
>> 1.3 without EAPI?? I ask for ditribution of binaries and want to know if
>> it makes no problems loading EAPI-enabled modules; or if I should
>
>Should work *I think*. It wouldn't work the other way around, of course
>(you can't load a non-eapi module into an eapi apache).
Not true. It's perfectly OK to load a Non-EAPI module into
an EAPI (ssl) compiled Apache. Just ignore the warning
about "This module might crash because it's not EAPI".
As far as loading an EAPI module into a Non-EAPI
compiled Apache... it depends on the module.
Might work, might not.
If it relies on the EAPI callbacks to get its job done
( instead of just the other regular hooks ) then it
probably won't work because the Non-EAPI Apache
won't be making the EAPI hook calls.
In a message dated 1/22/2003 12:27:07 PM Central Standard Time,
[EMAIL PROTECTED] writes:
> what can happen if I load a module compiled with EAPI flag into a Apache
> 1.3 without EAPI?? I ask for ditribution of binaries and want to know if
> it makes no problems loading EAPI-enabled modules; or if I should
Should work *I think*. It wouldn't work the other way around, of course
(you can't load a non-eapi module into an eapi apache).
