On Sat, Oct 30, 1999, Magnus Stenman wrote:
> > Sorry to be a bit off topic, but I'm very curious about
> > the two questions below...
> >
> > Does someone know if there are any plans to incorporate
> > the EAPI into mainstream Apache?
>
> There were, but somehow it never got included.
> Someone on the apache list apparantly had a better solution,
> which also has not been incorporated...
>
> Status on that, Ralf?
Status is that because of the proposed KEAPI the inclusion of EAPI was
suspended a few months ago and while people were still confused, Ben L.
implemented a third hook variant of EAPI hooks directly in the 2.0 source tree
(nice timing, yeah)....
And so EAPI (in the current form) was no longer completely required and I
stopped the attempt to include it. Now there are only things like MM left
which people want, but I'm tired of fighting for those things. As it looks to
me, with Apache 2.0 the task of mod_ssl will be simpler, but for some problems
we will certainly still need some sort of EAPI. Whether we can include the
remaining EAPI features into Apache 2.0 or not we will see in the future.
Yeah, I know, Ben L. will now certainly say that with his implemented hook
mechanism, EAPI is no longer needed for Apache 2.0. But I'm convinced this is
(still) not true...
> It is recommended to compile mod_perl statically.
> It's a mod_perl bug, I believe.
I wouldn't really say it's a "bug" in mod_perl. Doug tries hard to make it
stable and has certainly eleminated the real "bugs". But the problems mod_perl
has under DSO are IMHO related to internals in the Perl library itself (which
Doug cannot solve directly).
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]
