From new-httpd-return-3182-apmail-new-httpd-archive=apache.org@apache.org Mon May 01 13:31:28 2000
Return-Path:
Delivered-To: apmail-new-httpd-archive@apache.org
Received: (qmail 42484 invoked by uid 500); 1 May 2000 13:31:28 -0000
Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
Reply-To: new-httpd@apache.org
list-help:
list-unsubscribe:
list-post:
Delivered-To: mailing list new-httpd@apache.org
Received: (qmail 42462 invoked from network); 1 May 2000 13:31:28 -0000
Date: Mon, 01 May 2000 13:35:04 +0300
From: Eli Marmor
Subject: Re: Apache 2.0 API and mod_ssl
To: modssl-users@modssl.org
Message-id: <390D5DD8.46D23BF3@elmar.co.il>
Organization: El-Mar Software Ltd.
MIME-version: 1.0
X-Mailer: Mozilla 4.08 [Hebrew Support by elmar.co.il (X11; I; Linux 2.0.36
i586)
Content-type: text/plain; charset=iso-8859-8
Content-transfer-encoding: 7bit
References: <0A2FDC11F692D311AA730008C7B161F2CCE9AD@exbhbhmb04.us.dbisna.com>
<20000501100914.A86387@engelschall.com>
Sender: jim@jaguNET.com
Reply-To: modssl-users@modssl.org
X-Sender: Eli Marmor
X-List-Manager: Majordomo [version 1.94.4]
X-List-Name: modssl-users
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N
Hi,
I will try to be more risky than Ralf and to forecast something in
the future of Apache:
Currently, a major effort is focused in designing and developing a
"multi-layered I/O" into Apache. This will allow to put different
modules in separate layers, so the output of one module will be the
input of another one, etc. For example, the output of PHP may
include SSI commands (Server Side Includes, "shtml"), and so on.
(I must admit that years ago, when I heard about Apache the first
time, and I was told that it is very modular, I was sure that the
modules lay in separate layers, and I was amazed and disappointed
when I saw that the model is much more primitive and limited).
*IF* this will become a stable and safe implementation, there will
not be any need for EAPI or any other special API/hooks/whatever in
Apache; Just build your own layer - SSL layer - and chain it as the
last layer before passing the output to the client.
I emphasized the "*IF*", because - as Ralf wrote - there is a long
way for Apache2 yet to go (although I expect the first beta - not
alpha - to be as stable as other web-servers, such as IPlanet and
IIS). In addition, there is no guarantee that the layered I/O
project will succeed.
You probably read about "exciting" developments and new features of
2.0, like APR, MPM, etc.; Don't believe! MPM and the other features
which are mentioned usually, insert a lot of crap into Apache and
may even cause it to be unstable and too complex. The real surprises
of 2.0 are the layered I/O, and the changes in the configuration
model. If these 2 projects will succeed, we are going to have an
amazing and powerful web server (much more than now), with cool
features, and (finally!) ease and friendliness (the changes in the
configuration model may ease the development of GUI tools for REAL
management of Apache configuration). But these 2 projects are still
in question.
In any case, as Ralf wrote, it will not be clever to deal with 2.0
now, because its APIs are still in design.
--
Eli Marmor
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org