Hello Victor,
as the cited begger for DSO I might argue at this:
> Hm.
> 1. Why you need two httpd servers in first place ?
Because to avoid heavy memory consumption for all customer servers.
> 2. How much is memory penalty for not-used mod_ssl ?
>
That's not the point; If you want to be flexible you'll
need an monolithe apache server which supports all commonly known/used
modules such as mod_perl, mod_php3, mod_frontpage, mod_ssl, ...
If you combine any of these you'll have to maintain about
n^^2 different apache versions for your customers to avoid
allocation of unused memory within your servers.
> So I'm not sure that this will help ISP's at all (you still must reinstall
> apache!) while this will be help distribution creators (like me :-)...
>
Why not ?
You may just create a (completly) virtualized apache and provide
a httpd.conf with all commonly used modules activated.
Within the documentation you may just write:
'To enable mod_perl within your apache Server, just uncomment
LoadModule, AddModule and certain Perl* directives and restart
the server'.
This is exactly the same we'll do with our customers:
Keep the apache installation and just configure it to the
customers requirements.
> It's not good. For distribution creators will be FAR better to have separate
> patch file for Apache and separate mod_ssl distribution complable via apxs ..
> .
Well, the problem with crypto stuff will of course still exist.
But this is with and without DSO support for mod_ssl.
Jan
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
