With HTTP Keep-Alives it is a connection until it times out (or closes for
another reason). Hence someone reading a page (but not actively
downloading anything) could be "connected".
So i am not making up my own definition of "connection". The client has an
inactive connection to the webserver if http keep-alives is enabled and
used, and the "Current Connections" performance counter object shows this.
If you do a netstat -an on the webserver you will see that there is an
established connection between the webserver and client, which also
indicates that there is a connection.
HTTP keep-alive is explained in the HTTP RFC (2616)[1], chapter 8. You may
also want to read about it on the Microsoft website[2].
HTTP keep-alive is enabled by default on IIS 6.0 and probably also IIS 5.0
(i didn't have anywhere to check right now).
For data to transfer between two hosts, first a connection must be
established (opened). Once a connection has been established, the data can
be transfered. When the data is sent, the connection is closed. With HTTP
Keep-alive, the connection is not closed immediately.
So a connection does not exist _only_ during a download...
Read "Protocol operation in detail":
http://en.wikipedia.org/wiki/Transmission_Control_Protocol
"Transmission Control Protocol"
http://www.scit.wlv.ac.uk/~jphb/comms/tcp.html
[1]
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8
[2]
http://www.microsoft.com/technet/pr...IIS/ea116535-8eb9-4c80-8b14-b34418dbfe42.mspx
Bye.
--
Regards,
Kristofer Gafvert (IIS MVP)
http://www.gafvert.info/iis/ - IIS Related Info