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-07 21:41 ------- Look, the basic problem is that the underlying implementation used to support attribute holders is being used in error according to it's documentation (java.util.HashMap documentation). It doesn't just leave the data in an inconstistent state, but rather crashes systems. If the developer has to synchronize access to the session or application or context every where attributes are being set then why not change the base application (Tomcat) to do this already....basically the application, context, and session are useless if nothing can be stored in them. So, they have to be synchronized anyways, so this should be done at the Tomcat level. 5.5.x and 5.0.x really need to be fixed because it doesn't make sense not to. Basically I'm getting this from the conversation (and anyone else should be).....the spec says it's up to the developer to synchronize........the developer has to synchronize every where the attributes are set and get.....so what is the difference if Tomcat does it or the developer does it? Plus, does the spec also say it's up to the developer to synchronize request, context, and session attributes? It's been a while since I have read the servlet spec, but I have the 2.3 version on disk and will skim over it again, but even if the spec says it....it doesn't make sense not to synchronize code that has to be synchronized one way or another anyways. -- 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]
