AJAX requests would each be treated as separate requests - and (unless you are using sticky sessions) they could get routed to any node. They could also fire off independently within the code javascript code on the page - depending on how they are coded.
-- Robin D. Wilson Director of Web Development KingsIsle Entertainment, Inc. WORK: 512-623-5913 CELL: 512-426-3929 www.KingsIsle.com -----Original Message----- From: lightbulb432 [mailto:veerukrish...@hotmail.com] Sent: Wednesday, May 06, 2009 2:04 PM To: users@tomcat.apache.org Subject: RE: Cluster session sync question (from documentation) I just thought of something with regards to multiple requests from a given page - let's assume the browser doesn't generate multiple requests for dynamic content by way of frames or images. Are AJAX requests treated any differently from regular requests, whereby multiple AJAX requests from one page would somehow always be routed to one node even in the absence of sticky sessions? (Or could all those AJAX requests still end up modifying different session instances on different nodes, even though all requests were from the same page? Because that's a very likely scenario for most "rich" web applications these days.) I ask this out of curiosity, I suppose - after all, it seems like sticky sessions are the way to go and that would preclude the above issue completely. Caldarale, Charles R wrote: > >> From: lightbulb432 [mailto:veerukrish...@hotmail.com] >> Subject: RE: Cluster session sync question (from documentation) >> >> Request 1 goes to node 1. Am I correct in saying that as long >> as Request 2 reaches node 2 before the session from node 1 has >> fully replicated over, the the inconsistent session problem exists? > > That's my understanding - which is why the doc says to use sticky > sessions. > >> the session that persists would be either the session from >> node 1 or from node 2, but absolutely not both? > > Correct. > >> using what criteria would anyone decide against >> using them? What's the tradeoff here? > > Potential performance imbalance is the only thing I can think of. If one > of your clients creates a lot of requests, they'll all have to be > processed on a single node, leaving the others relatively idle. I doubt > that this is much of a concern in the real world. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/Cluster-session-sync-question-%28from-documentation%29-tp23411578p23413346.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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org