You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Jonathan Mangin <jo...@comcast.net> on 2004/02/18 16:39:04 UTC
[users@httpd] Apache compilation rules & module interdependencies
Hi,
Is there a text lying about that tries to explain interdependencies
of rules, modules and options when configuring/compiling Apache?
For instance, mod_perl (or perhaps mod_so or ??) wants to use the
EAPI. mod_vhost_alias and libphp4 seem to prefer not.
Thanks,
Jon
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Apache compilation rules & module interdependencies
Posted by Jonathan Mangin <jo...@comcast.net>.
----- Original Message -----
From: "Nick Kew" <ni...@webthing.com>
To: <us...@httpd.apache.org>
Sent: Wednesday, February 18, 2004 10:49 AM
Subject: Re: [users@httpd] Apache compilation rules & module
interdependencies
> On Wed, 18 Feb 2004, Jonathan Mangin wrote:
>
> > Is there a text lying about that tries to explain interdependencies
> > of rules, modules and options when configuring/compiling Apache?
>
> There are only two rules:
> (1) EAPI is for mod_ssl on Apache 1.x
> (2) Upgrading to Apache 2 rids you of this complexity once and for all.
>
> > For instance, mod_perl (or perhaps mod_so or ??) wants to use the
> > EAPI. mod_vhost_alias and libphp4 seem to prefer not.
>
> The issue is that 1.x can't support SSL cleanly, so mod_ssl introduces
> its own API (called EAPI). Most modules are source-compatible, but
> not binary-compatible, with either.
>
> 2.x fixes this by supporting SSL cleanly with the standard API.
> Once you upgrade, you find this is just the start of the benefits:
> the API being altogether more powerful makes it a great platform
> for things that would have required extensions like CGI, PHP
> or a tomcat backend on earlier servers.
>
>
> --
> Nick Kew
>
I see. Near-future project #4869. Thanks.
--Jon
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Apache compilation rules & module interdependencies
Posted by Nick Kew <ni...@webthing.com>.
On Wed, 18 Feb 2004, Jonathan Mangin wrote:
> Is there a text lying about that tries to explain interdependencies
> of rules, modules and options when configuring/compiling Apache?
There are only two rules:
(1) EAPI is for mod_ssl on Apache 1.x
(2) Upgrading to Apache 2 rids you of this complexity once and for all.
> For instance, mod_perl (or perhaps mod_so or ??) wants to use the
> EAPI. mod_vhost_alias and libphp4 seem to prefer not.
The issue is that 1.x can't support SSL cleanly, so mod_ssl introduces
its own API (called EAPI). Most modules are source-compatible, but
not binary-compatible, with either.
2.x fixes this by supporting SSL cleanly with the standard API.
Once you upgrade, you find this is just the start of the benefits:
the API being altogether more powerful makes it a great platform
for things that would have required extensions like CGI, PHP
or a tomcat backend on earlier servers.
--
Nick Kew
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org