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-14 16:45 ------- I am sorry if I am too late to push (the issue is already fixed), but in case it's not I have something to say: 1)SRV 15.1.7 says nothing about HttpSession being not thread-safe. And AFAIR this means the interface should be thread-safe. 2)SRV 7.7.1 says about synchronizing access to "session resources", but it says nothing about session object itself. If one thinks session itself was meant in it, he should agree that more exact method of synchronizing then "as appropriate" should be used in the specs: the Developer can choose any way it wishes to synchronize access to it's own resources but the method of synchronizing access to a object (HttpSession) that is used by different Developers (if such a synchronization is needed) MUST be defined. If you read "session resources" as "session", this means anyone can choose any appropriate method of synchronization of session object, that is totally incorrect. As for me, this means that neither 7.7.1 nor any other point of specs does NOT say that session object is unsafe and this means that in any implementation it MUST be safe. -- 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]
