> Ah! So what happens if your servlet takes a more than a few seconds
> between accepting the request and issueing the response? Will the
> browser display the first page it receives, and then then overwrite it
> with each subsequant page it receives?
Ok. I think you need to think about this a bit:
When you make a request this is what happens in terms of sockets.
tcp connection
user(browser) --------------------------> servlet
If you make a request to the servlet and then press the refresh
button before the servlet can respond then the browser simply throws
away it's end of the original TCP connection, thus you never see the
response from the first request.
You could see both responses if you opened another window for the
second response.
Clearly there is a one to one mapping between a browser window and a
TCP connection.
Therefore HTTP requests are always displayed in sequence, with the
last request you made being the one that is shown.
With HTTP/1.0 tcp connections are the same as HTTP connections, with
HTTP/1.1 there is an abstraction where many HTTP connections can share
a single TCP connection but the above still holds.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
