DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36541>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-20 00:06 ------- (In reply to comment #94) > If session attributes are now going to be synchronized as per spec, what about > servlet context attributes? They will face the same issue. The proposed (and now committed) change protects the attribute collection *inside* the HttpSession object, eliminating the opportunity for an application to cause that collection to become corrupted. But the fact that a session attribute can be accessed from multiple threads, and therefore might need internal thread safety checks internal to itself, is still the application designer's issue to solve. Indeed, it's not anything a container could do anything about, even if it wanted to. The attribute collection inside Tomcat's ServletContext implementation was already synchronized, and not subject to corruption. Only the technique used to represent *session* attributes was in question here. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
