Bill Barker wrote: > > While pooling was a very nice feature of JServe (which I have personally > taken advantage of in the past), the operative word in the spec is "may". > The 3.x and 4.0 implementations are entirely within their rights within the > spec to simply synchronize. > > In other words, this comes under the "if it itches, scratch it yourself" > clause of OS development. (personally, I can still tolerate the itching, but > would +1 someone else taking this on).
Personally, I don't have any issues writing servlets that are thread safe if performance is important, so I don't think I'll be contributing that part of the code (not to mention I probably wouldn't know how to write it). Actually, all my apps use one and only servlet, so that isn't all that difficult to do (just one of the benefits of using Velocity ;-) So, if I understand you correctly, TC 3.3 is compliant to the spec and it uses synchronisation, rather then pooling, to achieve the compliance. If yes, I'll close the bug as it is non existent. Bojan
