🚀 go-pugleaf

<emerson.pardo@gmail.com> wrote in message
news:1179780948.075616.164470@x35g2000prf.googlegroups.com...

> If I set TIdHTTPServer KeepAlive property to true the server
> will try to keep all conections keep-alived?

Only for those connections where the client actually asked for the
connection to stay alive after the response has been sent.  Otherwise
no.

> What does happen if one client send some requests with
> keep-alive enabled and others requests with keep-alive disabled?

Each request is handled independantly.  If a keep-alive is not used on
one request, then that connection will be disconnected after the
response is sent.  The client would then have to reconnect to send the
next request.

> My server is a stock quotes server and my client needs to start
listen
> some stock quotes so it sends one request (with keep-alive disabled)
> for each stock it wants to listen.

Then the client is going to have to reconnect on each new request.

> When my client begins it opens one connection with keep-alive
enabled
> and when the stocks updates his data the new values will be sent
through
> this connection. Now what is happening is that the server doesn't
keep
> this connection opened and I'm not understanding what is happening.

Then the client is likely not requesting a keep-alive in its request
to begin with, so the server's KeepAlive option is ignored for that
connection.


Gambit