tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: [PATCH] SingleThreadModel Pool for TC 3.3
Date Sat, 27 Oct 2001 03:12:28 GMT
As promised, I've just checked this in.  I've modified the original patch
slightly so that the configuration can be set as options to
Servlet22Interceptor.  I've also added an option to disable pooling so that
we don't get flooded with "why doesn't my CounterServlet work anymore"
messages.  Hopefully this will end the recuring "how to handle STM servlets"
debate (at least on the 3.3 side of the list ;)
----- Original Message -----
From: "Schreibman, David" <>
To: <>
Sent: Thursday, October 04, 2001 4:58 PM
Subject: [PATCH] SingleThreadModel Pool for TC 3.3

> I'm submitting this with mixed feelings since the recent discussion has
> shown strong opinions about the utility of the SingleThreadModel.
> I was already in the middle of doing the work when all that came about so
> went ahead and finished it.  After reaping the benefits of Tomcat for a
> couple of years I've been wanting to give something back.  So after a
> post about how to help, I went into bugzilla and found this issue.  I
> even use STM, but was somewhat familiar with the ServletHandler and
> I could contribute here.
> At a minimum, I had fun doing the work and was able to learn a bit more
> about the code base.
> Maybe it will be of some use to others.
> Looking forward to more good stuff from this project!!
> -David


This message is intended only for the use of the person(s) listed above 
as the intended recipient(s), and may contain information that is 
PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
you may not read, copy, or distribute this message or any attachment.  
If you received this communication in error, please notify us immediately 
by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent 
through the Internet is not secure. Do not send confidential or sensitive 
information, such as social security numbers, account numbers, personal 
identification numbers and passwords, to us via ordinary (unencrypted) 

View raw message