I am concerned about a problem and I am sure others have either solved it,
or figured it really isn't a problem for one reason or another.
I have a set of servlets that make use of HttpSession during their
processing. If a single client presses a button on their form twice they
will send two requests to the app server at the same time. Does this cause a
race condition in which servlet thread 2 might write to the HttpSession and
then thread 1, but thread 2 returns the page to the browser so now the data
in HttpSession isn't quite correct (it's the result from thread 1 not thread
2).
The servlet spec seems to say it's up to the developer to cope with this
problem - I need to make sure that the page the user is looking at
corresponds to the state of their session in the app server.
Is this really a problem? Is there a simple or well known way to cope with
this?
Cheers
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
