> From: Nenad Kovacevic [mailto:micami...@yahoo.com] > Subject: RE: Getting the Right High Availability Architecture for > Tomcat > > Our applications do not issue concurrent requests to the servers, i.e. > they are classical web applications where the user activates a control > on a page and then waits for a page to refresh or a new page to load.
Unless the pages are incredibly simplistic, there will be multiple concurrent requests. Each embedded object in the page along with any .css files will cause the browser to issue multiple requests in parallel. You also have no control over the user getting impatient and clicking more links or buttons before the prior one responds. > However we warn the users to use only controls on the page and gray-out > submit buttons once a request is submitted so hopefully this should not > be an issue. Sorry, but that's rather naive. You cannot base the integrity of your application on trusting the user to always do the right thing. > With such an application in mind would you see an issue with not > implementing sticky session? Yes, I would. - 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
