1 There is no keep alive in asp server client intercource, as far as I
know.
Is this relevant to asp server? I thought that this is relevant to HTTP and
a server which manages HTTP
2. Only thwe client can ask for more information by rewesting a new page
This is how thing are working most of the time. But are you sure about
"Only"?
Consider this:
A Client sends an HTTP request. Webserver replies to it with an HTTP
response. What prevents the Webserver from sending a second response along
the same route?
3. REMOTE_HOST in Request.ServerVariables - does it mean the IP (static or
dynamic) adress of the computer, generated the HTTP request?
4. [1 By topposting]
If you mean my message timestamped 1.5 hours before yours - I have nothing
to do with this for these 1.5 hour give no advantage and secondly, I
understand that this can only be done by wrong time set on my. As of this
writing I have 10:14 am UK time on my machine
"Evertjan." <ex**************@interxnl.net> wrote in message
news:Xn********************@194.109.133.29...
aa wrote on 04 feb 2004 in microsoft.public.inetserver.asp.general:
Clients are not connected to a page, they just get a html page
downloaded.
This shows there is no keep alive in connection with the browser.
I appreciate that.
But a client stays connected (Connection:Keep-Alive) to the server (I
guess) which I interpret as a possibility for the server to use this
connection to send information.
Where am I wrong?
You are wrong
[1 By topposting]
2 There is no keep alive in asp server client intercource, as far as I
know.
Only thwe client can ask for more information by rewesting a new page.
(I hope we are not talking asp.net [OT on this NG] which perhaps fakes a
connection by adsking for iframse or so. I knowe nothing about that.)
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)