|
From: Scott Klement <klemscot@klements.com> > No, HTTP is not "connectionless". When you get something from a web > server, you connect, you request a document, it sends it, you request > the next, it sends it, etc... all during one TCP connection. The "etc" bothers me. How does it know when my current request is going to be the last? The only way this can happen is that the connection times out after a (long!) time, because I can sit there staring at a webpage for hours before requesting "the next all during one TCP connection". Something fishy here....
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.