In 1.3.x, it was so happening that Apache/mod_ssl registers the connection
id (fd) with OpenSSL, and then OpenSSL takes over the connection handling as
well as the protocol communication stuff from that point onwards..
In 2.x, with the introduction of filters, OpenSSL nolonger talks directly to
the client directly.. Instead, all the data comes/goes thru' the filters
(*_NETWORK_*).. The connection handling stuff is done at the APR level..
Thus, the OpenSSL is used only for the protocol logic ONLY and not for
handling any connection details.. Pl. let me know if you need more details..
Thanks
-Madhu
-----Original Message-----
From: Sunitha Kumar [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 29, 2001 9:39 AM
To: [EMAIL PROTECTED]
Subject: Re: mod_tls
could some one give pointers on the need for filters around the ssl
code. What would be lost if those filters don't exist. And, what was the
need to put them in, originally.
thanks,
sunitha
Gonyou, Austin wrote:
>The referrence here is one about all the filters used by apache 2.0. If
>there is a filter bucket in APR, it's understandable that Apache 2.0
modules
>will have 2 parts. The logic piece and the filter piece. As far as I can
>tell, the filter mechanism allows for some distinct advantages and makes
for
>a very flexible configuration framework. My issue here is that if mod_tls
is
>sacrificed, then what's the point of using filters at all anyway? That
said,
>could it be said that you CAN write a module for Apache 2.0 without needing
>the use of filters? If so, then that makes sense.
>
