Re: Metuxmpm test failed

-                                                 [email protected]
---------------------------------------------------------------------

On Mon, Oct 06, 2003 at 10:29:18AM +0400, Dmitry P. Schegolev wrote:

<snip>
> > too slow, too resource intensive.
> Why? What difference? Now separate apache program do the same. It's called 
> multiplexer. As I understood, It now use unix socket to transfer data to 
> apache process. I don't see any difference.
Yes. But it does some tricks, i.e. passing the whole socket.
We do not process the whole request in the multiplexer.

> <snip>
> 
> > there are several reasons, i.e. reusing mod_ssl for ssl handling and
> > other similar cases.
> 
> Now we have problems with mod_ssl, and as I see, great problems. And if 
> mod_ssl be a separate module between tcp socket and ordinary apache, life 
> would be easier.
But much slower.
You should hold in mind, that apache should also work on very high load.
Currently it really seems to be the best webserver for those jobs - I
dont like to change this ;-)

> I think it's more cleaner structure, than tomorrow apache structure.
Yes, it is cleaner, but much slower. Your approach requires the whole
data to be passed over multiple process boundaries - this produces load.

> You don't want ssl? Omit ssl_handling_module in configuration!
> You don't want multiplexer? Omit it!
Where's the difference from today ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT services

 phone:     +49 36207 519931         www:       http://www.metux.de/     
 fax:       +49 36207 519932         email:     [email protected]
 cellphone: +49 174 7066481	     
---------------------------------------------------------------------
 Diese Mail wurde mit UUCP versandt.      http://www.metux.de/uucp/