GB Developer wrote: > > 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.
The servlet spec 2.5 draft says in SRV 2.2.1. (should be similar in 2.4.). Even spec 2.3 had this warning note eventhough in 2.3. SingleThreadModel wasn't deprecated: "Objects that are accessible to more than one servlet instance at a time, such as instances of HttpSession, may be available at any particular time to multiple servlets, including those that implement SingleThreadModel." So this was one of the reasons to deprecate this. Chuck and you are right. I described ways to achieve concurrent access to one session using multiple servlets (or multithreaded access). Just think of frames or the infamous IE double submit problem for more examples. Cheers, Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
