On Sun, 30 May 1999, Ralph Clark wrote:
> Do you happen to know why, after a long period of inactivity, my browser would
> still be maintaining an open TCP/IP socket to a remote host?
The HTTP 1.0 protocol used a separate TCP connection for each
request/response. Studies show that connection set up and tear
down is a significant cost when dealing with the sort of small
chunks of data normally carried by HTTP. The newer HTTP protocols
allow batching of requests and responses so it makes sense for
a browser to hold on to a connection for a while. Probably not
for a "long period of inactivity" though. The other end likely
closed the connection ages ago but with your link down you would
have never received a packet to say so :-).
Mike
--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: [EMAIL PROTECTED] |
| 280, Silverdale Road, Earley, | Voice: +44 118 926 6996 |
| Reading RG6 7NU ENGLAND | Work: +44 118 989 0403 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
