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-08 00:36 ------- I've been following this with a lot of interest ever since Leon raised the issue yesterday, and I discussed it with some folks at work today a bit. Looking at this strictly from a developers' point of view, I could care less what the specs says, and I could care less why the Tomcat code is the way it is. The bottom-line is that if I call session.getAttribute() or setAttribute () in a servlet or Struts Action or whatnot, I do not expect there to be any chance of the internal data structures getting corrupted, or me getting back inconsistent data, and I most definitely do not expect there to be any chance of a server hang or crash, and I do not expect to have to do anything myself to ensure any of this. Any other answer is, to me and to those I spoke to, just plain wrong. I am in absolute agreement with those saying this needs to be fixed. I do not recall ever having been bitten by this problem, but it's just subtle enough that I might not have known if I did. I don't think anyone is looking to place blame here. I don't care what was originally in the Tomcat code and what is there now or why it was changed. This simply comes down to a legitimate issue that needs to be resolved. It's not even a minor issue frankly, it's a pretty substantial one, regardless of the fact that it apparently hasn't caused huge problems for everyone. If the spec needs to be fixed, no problem, contact who needs to be contacted and let them know. But that DOES NOT mean you serialize and wait for them to do their thing. There is a solution here that, to my understanding, isn't contrary to the spec as it exists today anyway, so not following through with it is kind of silly. I'm sure any number of people would be willing to submit a patch for this if it's an issue of not having time, but to be arguing about whether it should be fixed or not doesn't seem to be reasonable on this one. -- 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]
