There's something I really don't understand here. It seems that what
people are saying is that javax.servlet.http.HttpSession is not
thread-safe, which I assumed it was. Would wrapping the HttpSession object
in a synchronized class fix the problem? What would I have to synchronize
on? Is the Object returned by HttpServletRequest always guaranteed to be
the same? I would think not. There are servlet implementations that store
sessions across multiple VMs or even multiple machines. What do I do there?
At 12:50 PM 5/5/99 -0700, Rod McChesney wrote:
>It also has serious performance implications. Acquiring locks is
>quite expensive, and for many uses it's not required. For instance,
>read-only beans that initialize themselves at once when the session
>is created would never need synchronized access, so doing it to be on
>the safe side would slow things down for no purpose.
>
>Rod McChesney, Korobra
--
Ben Engber
Software Engineer
The New York Times
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
