Re: Metuxmpm test failed

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

>
> > separate program, not apache program, which only get data from tcp socket
> > and multiplex it to ordinary apache process rely on http header.
>
> 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.

<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.

tcp_socket -> ssl_handling_module -> multiplexer -> apache_fork

I think it's more cleaner structure, than tomorrow apache structure.
You don't want ssl? Omit ssl_handling_module in configuration!
You don't want multiplexer? Omit it!

Best regards,
Dmitry.

P.S. May be it offtopic, sorry :)