Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Keep Alive | 11 comments | Create New Account
Click here to return to the 'Keep Alive' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Keep Alive
Authored by: digitalone on Jan 25, '03 06:17:33AM

The keep alive option mentioned in user prefs is a good one, but it can only ATTEMPT to keep the connection alive. Most servers will kill the connection by changing their state automatically, forcing the connection closed. If set-up right, and many servers do this to prevent Denial-of-Service attacks, they will kill the connection without waiting or the remote host to ACK if the state exists where there are multiple requests made from the same remote host for different pages while the previous TCP session is still established with the same host.
You're right in that HTTP 1.1 supports pipelining, otherwise you would have to create a new connection every time you pull any embedded component in a page [such as images or Java applets, etc]. It's scope can be severely limited by constraints made on the server, however. On commercial or busy servers, typically open connections are set to close immediately after all data is transmitted, and the link is kept open b the scripting embedded in the HTML/XML whatever.

Digitalone
This, however, is one man's humble opinion.



[ Reply to This | # ]