On 9/7/07, lightbulb432 <[EMAIL PROTECTED]> wrote: > > I'm reading some book concurrency books that talk about potential thread > safety issues with HttpSession. Specific cases follow: > > - When the web container passivates an HttpSession while a user's request > modifies it
strange use case. why should that happen? > - When the web container replicates an HttpSession while a user's request > modifies it Hmm.. Is it a real issue for you? > - When multiple quick, successive requests from the same user access the > same HttpSession No problem here, at least not with 2.5 compliant server. regards Leon > > Could somebody explain how Tomcat deals with the first two, and what steps > web application developers need to take to avoid concurrency problems with > all three cases above? Is it guaranteed that the passivated/replicated > object is always a consistent view of the HttpSession? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Concurrency-with-HttpSession-tf4403264.html#a12561600 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
