I wouldn't get too hung up on the internals of tomcat here. You should
remember servlet engines can be implement the spec in any way they see
fit. They are only required to comply with the spec. Anything not
spelled out there is subject to interpretation.
Suffice it to say servlets in and of
Evan J wrote:
On 3/30/07, David Smith <[EMAIL PROTECTED]> wrote:
Quoting the spec here (SRV.2.1 of servlet spec 2.4):
"The handling of concurrent requests to a Web application generally
requires that the Web Developer design servlets that can deal with
muiltiple threads executing within the s
On 3/30/07, David Smith <[EMAIL PROTECTED]> wrote:
Quoting the spec here (SRV.2.1 of servlet spec 2.4):
"The handling of concurrent requests to a Web application generally
requires that the Web Developer design servlets that can deal with
muiltiple threads executing within the service method at
Quoting the spec here (SRV.2.1 of servlet spec 2.4):
"The handling of concurrent requests to a Web application generally
requires that the Web Developer design servlets that can deal with
muiltiple threads executing within the service method at a particular time.
"Generally the Web container
Hi,
I am new to servlets and web container. From what I have read so far,
I've gotten an impression that the web containers, in this case
Tomcat, create only _one_ instance of each particular servlet upon
start/[re]deployment of a web application. Any request to such servlet
would cause a contain
