Costin Manolache wrote:
>
> >
> > The solution seems to split the initial problem in 2 parts :
> > 1 : the keepalive feature.
> > . every httpd opens a socket -> one servlet engine (default server if
> > load-balanced config)
> > . the socket is not closed by the httpd. it is reused and reused.
> > . if the socket is closed by the servlet engine, httpd opens a new
> > one when needed.
> > . the servlet engine accepts incoming connections from httpd
> > processes (belonging to 1..n Apache servers)
> > . once accepted, a thread block on the socket to read new requests
> > (keepalive).
> > authentication is performed once, and the load-balancing parameter
> > (the servername to add to the cookie) is sent once.
> > . if a servlet engine whishes, some of the opened sockets can be
> > closed.
> > This should give a boost to performances, as the socket creation has
> > a huge cost.
> >
> > 2 : the new protocol (possibly) bi-directionnal protocol), built on top
> > of the the above keepalive enabled connections.
> > . ajpv11 like. (not very clever, but everything is there).
> > . ajpv21 like (with multiple packet exchanges in one single request
> > (yes, including requests servlet engine -> Apache).
>
> If it helps, I already did all that, the code is in
> tomcat/src/native/apache/modules/mod_ajp23.c
>
> It does increase the performance, and it seems to work fine.
>
> ( also should work over Unix domain sockets )
>
> Costin
Cool ! I'm going to look at this code. Thanks for the info.
Why isn't this the default protocol&module for Tomcat with Apache ?
Jean-Luc
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
