> On Sat, Oct 24, 1998, Ralf S. Engelschall wrote:
>
> > Just for your information and to share my great happyness ;-) :
Most excellent ;-)
> Four additional module hooks, a generic low-level hook mechanism and a
generic
> context mechanism. All three thing together provide a way to _loosely_
couple
> mod_ssl into the Apache core code instead of couple it via direct symbol
> references (the big NO-NO for DSO). This way even inter-module
communication
> is possible: For instance mod_log_config's SSL support is now loosly
coupled
> to mod_ssl, too. This way mod_log_config has not even to be linked
against
> SSLeay ;-)
There are two things I'm curious about:
First, do you have any kind of performance penalty figures? Not
that my Net connection could in any way saturate my apache on my
<insert fast processor here> box, but I'd be interested nonetheless.
The second thing: are your patches to the core code folded back
into the main apache code? I understand that the apache group did
not want cryptography code in the main code base, but if your patches
only add "generic hook mechanisms", there could be a chance that we
wouldn't need the apache.patch with 1.3.4 or 2.0 ;-)
Regards,
Hakan
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
