Also, HTTP keep-alives can cause their own problems because
they tie up a server thread until either the client says to
close it (fat chance that will happen in a web app) or it times out.

I'd be very surprised if keep-alive tied up a server _thread_. Keep
alive tells the server not to close the TCP socket, a performance
improvement since there are several roundtrips required to open a new
socket connection, but I can't imagine that a web server would dedicate
a thread to a socket that was waiting for a new request. Speaking only
for IIS (since it's the one I know best) IIS does _not_ dedicate a
thread to that keep-alive socket.

-Walden


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.