On Thu, Oct 28, 1999, Adriano Rodrigues wrote:
> Does someone know if there are any plans to incorporate
> the EAPI into mainstream Apache?
There were plans but because of two other nice guys :-( EAPI didn't went into
Apache 2.0 (the first one confused the group and stopped consideration with
his own EAPI variant and the second guy took the chance and reimplemented the
third variant directly for Apache 2.0 in the meantime). So EAPI as it exists
currently will not directly go into Apache 2.0, but parts of it will go into
Apache 2.0.
> Also, I usually compile a bare bones Apache with EAPI and all my
> modules are DSO (mod_ssl, php, mod_perl, etc).
>
> But when one starts getting segfaults (mod_perl comes to mind),
> people usually recommend that you build Apache statically.
>
> Are the problems due to Apache's DSO implementation (is it rock solid?),
> bugs in the modules, or both? Of course, I am assuming here that the
> environment is sane (a modern UNIX like FreeBSD or Linux, libs
> compiled with -fpic, etc).
There is no "Apache DSO implementation". We are just using dlopen(3) and
friends. The problems in the DSO area is mainly related to side-effects the
large modules like PHP3 or mod_perl have under DSO situation. Although there
are known problems with some DSO implementations of Unix flavors, the actual
problem are most of the more caused by bugs in the modules or actually in
third-party libraries which are used by the modules.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
