On Wed, 10 Sep 2003, Jing Zhou wrote: > [snip] > It is very likely for the browser window to use the same connection to send > request A and B (with the keep alive setting). But I am not 100% sure for > this. Any Tomcat users or experts could provide some clue? >
This is actually more an issue of the client than the server. Tomcat 4.x and 5.x do, in fact, support HTTP/1.1, which includes the ability to send more than one request serially on the same TCP connection. However, if you're doing scenario (a) from my previous response (user presses STOP), then the client knows it needs to switch to a different TCP connection because it hasn't received the first response yet. In scenario (b)-(d) -- for example, multiple <img> tags -- the client will open separate TCP connections for simultaneously pulling images (Netscape used to default to 4). Under no circumstances will a client that correctly implements HTTP send a second request on the *same* TCP connection as a previous one without having received a response yet. Of course, whether it's the same TCP connection or a different one makes absolutely no difference in the fact that you do need to deal with the SUBMIT -- STOP -- SUBMIT behavior of users. How the client and server communicate (one socket versus many, one request per socket or persistent connections) is an irrelevant technical detail. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
