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=40531>. 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=40531 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2006-09-18 10:16 ------- I can't discuss this with JSR-154 team because it's not specified how this particular case should be handled. I'm refering SRV.7.7.2 section of the Servlet 2.4 spec wich Tomcat implements in recent versions. Nowhere in that document sticky sessions are mentioned and only general comments about serialization and concurrence are provided. In fact it says that "Migration of sessions will be handled by container-specific facilities." so implementations are free, and because SavedRequest info is saved as a note in Tomcat's Session that's why we ask it to be Serializable and/or stored in the session and not as a non-serializable-internal note. -- 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]
