You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Ralf S. Engelschall" <rs...@engelschall.com> on 2000/05/01 10:09:14 UTC

Re: Apache 2.0 API and mod_ssl

On Sun, Apr 30, 2000, Zakon, Stuart wrote:

> Are there any sources which describe how the Apache 2.0 API
> will affect future mod_ssl integration?
> 
> In particular we are interested in how the EAPI might be affected
> since we are currently implementing a module which leverages
> the client 'hooks' in the EAPI.

The Apache 2.0 API is still horribly in flux (and IMHO still far away
from a real and clean API on which one can count). So it is even still
not clear to myself how the Apache 2.0 API and Apache 2.0 itself will
finally affect the future of mod_ssl. At this point I'm myself still not
convinced that Apache 2.0 actually has a reasonable future at all :-(

Apache 2.0 already contains partial functionality which can replace
EAPI, but not all of EAPI. We could add the remaining EAPI functionality
to Apache 2.0, or rewrite mod_ssl to no longer provide functionality
which is now based on EAPI, or ignore the Apache 2.0 issue at all and
stick with Apache 1.3. Which way we go is still not clear. Perhaps there
are more possibilities I've still not recognized. We will see...

The whole decisions have to be delayed until Apache 2.0 settled a lot
more and especially until the politics behind Apache 2.0 become more
clear (especially the involvement and intentions of some vendors).
Because at this stage it is far away from clear where Apache 2.0 will go
and why it goes this way (I know that some of us will not agree with my
point of view here).

There are issues in the Apache 2.0 development which we have to still
observe before implications can be made (like the fact that more and
more non-Unix platforms are worked on while focus on Unix flavors
decreases dramatically; the fact that important technologies like
Autoconf and DSO are used too thoughtless and without enough care; the
fact that the 2.0 API will be as unclean as the 1.3 API because people
have no priority on creating a well-thought out API, etc.). So currently
IMHO it is a pure waste of manpower to pre-port mod_ssl to Apache 2.0,
because it would end in a maintainance desaster until a 2.0 release
version is available. And because of the same reasons I still cannot
give you a reasonable statement how Apache 2.0 will affect the future of
mod_ssl. I've a few plans for mod_ssl under my desk, but nothing I can
share in public.

The only point on which you can count is the same as the point I count
on: If you program with EAPI, you can be sure that both your module
will run the next 12 months without problem (because Apache 2.0 will
certainly require this time until it is ready for production) and that
guidelines to convert from EAPI to Apache 2.0 API will be available
later, too. And you can be sure that mod_ssl will exist in the future,
too ;)

Yours,
                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

    I don't know if it's what you want, but it's what you get.
               -- Larry Wall
    What you see is all you get.
               -- Brian Kernighan

______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      modssl-users@modssl.org
Automated List Manager                            majordomo@modssl.org


Re: Apache 2.0 API and mod_ssl

Posted by Eli Marmor <ma...@elmar.co.il>.
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