> Edward Ivanovic at [EMAIL PROTECTED] wrote: > > > That's incredibly frustrating as there are very valid cases where you need > > to use the SingleThread model and still support more than 1 user. The > > SingleThreadModel is a necessary API - I don't think nothing horrible about > > it. As for thread safety, that's something programmers need to learn. > > > > But anyway, thanks for the response. At least now I can stop wasting time > > looking through the documentation for the 50th time. I'll also look at the > > archives. > > > > Is there another free/cheap app server out there that supports > > SingleThreadModel with multiple servlet instances? > > > You're more than welcome to use any of the other servlet containers > supporting SingleThreadModel
I wouldn't be against adding some quality instance pooling code to the StandardWrapper, but that would have to be contributed (ie, I'm not going to do it, since I don't think it's useful, but if somebody does it for us, no problem :)). > (at the same time I'll lobby for its removal in > the next Servlet specification) I think the best you can hope for is "deprecated". Remy
