All requests will keep executing. The user should get the last result. Hitting reload forces the browser to drop its connection and open another one to the server I think. The server doesn't know the connection has gone AWOL until it tries to send data to the client. --Angus
> -----Original Message----- > From: Hans Wichman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 2:42 PM > To: [EMAIL PROTECTED] > Subject: request/session handling > > > Hi, > > can anyone tell me what happens if a user requests a servlet > which might > take 5 seconds to complete the request, and the user starts > hitting reload > a number of times? (I know the typical programming answer is > 'why?! why > would the user do such a thing?' but I am afraid I'm gonna > have to give a > better answer than that). > Will the already running requests be aborted, will they > complete, which > output from which completed request will make it back to the user? > I am asking because it appears the servlet can handle two requests > 'simultanously' from the same user, which means I have to > synchronize on > objects in this users session, even if there is only one user > using the > application. > > Hope anyone can help. > greetz > Hans > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
