I think the http protocol does not allow the parallel processing of requests
using a single connection.
At least the response of a following request cannot pass the
predecessor on the same connection.
(How could the responses be matched to the requests?)
So parallel processing is not really useful on a single connection.
If a client/browser wants to have parallel processing it uses more
than one connection to a server.
Karl-Heinz
----- Original Message -----
From: "Feng Xie (fxie)" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Sunday, June 19, 2005 5:25 AM
Subject: RE: Re: configuration question : the number of connections could be
supported by a connector in Tomcat 5.0
Bill:
Thanks for your answer. In my case, the client just directly talks to
Tomcat. So, the maxThread means maxConnections.
Is it possible for Tomcat ( any version which supports HTTP/1.1
pipelining)'s multiple threads to work on *A same* connection at the
same time. I mean, due to pipelining, there might be multiple HTTP
requests in this connection waiting for process , therefore, multiple
threads in Tomcat are working on processing those pipelined requests
simutaneously -- each thread handling a single different request.
-Feng
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: Friday, June 17, 2005 10:47 PM
To: tomcat-user@jakarta.apache.org
Subject: Re: configuration question : the number of connections could be
supported by a connector in Tomcat 5.0
If you are fronting with Apache, then the mapping between connections
and threads is more a function of your MPM. As a result, I'm just going
to answer for the stand-alone Connector.
In Tomcat 5.0, there is a one-to-one mapping between socket connections
and threads. Pipelined HTTP/1.1 keep-alive connections will all use the
same thread to process. In 5.5.10+ this will no longer necessarily be
the case.
It will be possible for Tomcat to handle many (and the value of 'many'
is heavily dependent on what your app does :) more socket connections
than the configured maxThreads.
"Feng Xie (fxie)" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
.
I like to get some help on how to configure the maximum number of
connections could be supported by Tomcat5.0.
There is one config attribute called "maxThreads", according to Tomcat
doc, which is " The maximum number of request processing threads to be
created by this Connector, which therefore determines the maximum number
of simultaneous requests that can be handled. ".
My question comes from the fact that there might be multiple HTTP
requests pipelined in each HTTP/1.1 connections, so can we still treat
the "maxThread" as the maxConnections.
Thanks in advance,
Feng
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
