I've looked at it, and will check it in after 3.3 goes final. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 04, 2001 6:07 PM Subject: Re: [PATCH] SingleThreadModel Pool for TC 3.3
> Thanks David. > > I don't like STM, but since it's part of the spec we need to support it. > And since you spent the time to write it, I think we have the duty to > check it and find a way to check it in:-). Unfortunately, > not for 3.3, it's too late. But 3.3.1 can include it. > > Costin > > > On Thu, 4 Oct 2001, Schreibman, David wrote: > > > 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 I > > 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 recent > > post about how to help, I went into bugzilla and found this issue. I don't > > even use STM, but was somewhat familiar with the ServletHandler and figured > > 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) e-mail.
