Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Smith wrote:
As I understand it one instance of the servlet per webapp is accessed
from all threads in a reentrant manner. This is why you normally can't
use any class instance variables in a servlet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Smith wrote:
> As I understand it one instance of the servlet per webapp is accessed
> from all threads in a reentrant manner. This is why you normally can't
> use any class instance variables in a servlet.
While this is the most straig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pavan,
Pavan Singaraju wrote:
> I have a basic question about servlets in Tomcat 5.0.18. In theory, when
> there are simultaneous requests come for a servlet, it will either queue the
> requests and serve one by one or create multiple threads of t
Pavan Singaraju a écrit :
I understand that Tomcat has a SingleThreadModel interface that allows
only one thread access/One request at a time model. But help me solve the
previous problem
--
Pavan S. Kumar
Don't use SingleThreadModel anyway. From J2EE 1.4 docs:
Deprecated. As of Java Ser
Pavan Singaraju wrote:
Hi,
I have a basic question about servlets in Tomcat 5.0.18. In theory, when
there are simultaneous requests come for a servlet, it will either queue the
requests and serve one by one or create multiple threads of the servlet and
serve the request.
My question is, wh
> From: Pavan Singaraju [mailto:[EMAIL PROTECTED]
> In theory, when
> there are simultaneous requests come for a servlet, it will
> either queue the
> requests and serve one by one or create multiple threads of
> the servlet and serve the request.
> My question is, what / how tomcat handles this
Hi,
I have a basic question about servlets in Tomcat 5.0.18. In theory, when
there are simultaneous requests come for a servlet, it will either queue the
requests and serve one by one or create multiple threads of the servlet and
serve the request.
My question is, what / how tomcat handles
