-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
This would indeed lock that particular session, but you have to think about
are you locking it *from*? That session object is unique to a particular
user, because each user has their own session. It will only be accessed
from
multiple threads simultaneously if the same user is making simultaneous
requests -- possible in a framed environment, but pretty unusual otherwise.
Unfortunately, a small part of our site includes frames. This and redirects
seem to cause problems for a specific user because he/she is reading or
writing information to their session simultaneously.
Your explanation on locking an object contained in the session is good. The
servlet touches a lot of information in the session which is why I was
thinking I needed to synch the whole session in order to prevent the servlet
from overwriting the information in a session while another instance was
reading it. I suppose I need to revisit my implementation?
-- Josh
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
