An HttpSession is an interface, so there's no telling whether the underlying
routines
are synchronized or not; that depends on the servlet container. Hence,
whether you
need to synchronize operations yourself depends on your framework.
If you don't allow independently working
frames in the browser, and if you assume that the user won't open multiple
browser windows,
then you don't need synchronization -- there's only going to be one thread
accessing the
session data at a time in that framework.
If you're not sure about whether those assumptions apply to your case,
however, go ahead and add
synchronization. The overhead isn't all that much, especially when you're
talking about
a small number of accesses per request.
Duane Morse, Eldorado Computing Inc., Phoenix AZ
___________________________________________________________________________
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
