I have a question about the section from the documentation below: Distributed locking and pages using frames Tomcat does not keep session instances in sync across the cluster. The implementation of such logic would be to much overhead and cause all kinds of problems. If your client accesses the same session simultanously using multiple requests, then the last request will override the other sessions in the cluster.
How, for example, would a client be able to access the same session simultaneously? (Because for non-simultaneous requests, wouldn't each request's changes to the session be replicated to all nodes in the cluster before the next request?) Could someone give examples of the unwanted consequences of this overriding of existing sessions from new requests? I'm just not really wrapping my head around this. Thanks. -- View this message in context: http://www.nabble.com/Cluster-session-sync-question-%28from-documentation%29-tp23411578p23411578.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
