> -----Original Message----- > From: Duan, Nick [mailto:[EMAIL PROTECTED] > Sent: Friday, January 06, 2006 5:14 PM > To: Tomcat Users List > Subject: RE: Single Thread is deprecated? > > Typo due to my laziness. I knew someone was going to catch > this. Actually the sentence should read: ... because there > is only one servlet that is active during a single user session. > > In other words, there is no way a single user session > (represented by a worker thread) can access more than one > servlet at a time.
Yah, I don't think that's right either, and besides that, it's a little backwards to describe it as you have. A sessions doesn't so much access servlets, as the servlets (more than one, regardless of their single-threadness) can access a single Session at once. Sessions are (never?) thread-safe. Which is perhaps one reason why SingleThreadModel was deprecated. People thought by using that interface that they would never have to worry about synch issues again. Even if you have nothing but singleThread servlets, that only prevents concurrent access to that servlet. Neither singleThread servlets nor any other mechanism I'm aware of can prevents concurrent access to a single Session object. Perhaps Remy will weigh in again with so many wildly varying 'opinions' ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
