Angus Robertson - Magenta Systems Ltd wrote:
should I add a new connection state hcIdle for it
Yes, a new THttpConnectionState makes sense, but do check the code
carefully to see what else is dependent upon it.
On a second look the existing hcRequest state seems to be the state that I
am
On Wednesday, July 03, 2013 12:04 PM [GMT+1=CET],
Tobias Rapp wrote:
As the last changes in this area have been made by Arno I have
included him in CC of this mail.
Huh? It looks like Angus added hcSendData to the THttpConnectionState.
I must admit that I have not yet updated my own webserver
This works as long as the connection is'nt idle for longer than the
value configured in KeepAliveTimeSec (which defaults to 10 sec). In
that case the connection is terminated by the server
Never really looked at KeepAlive. From the naming it sounds like a means
of keeping an idle
Angus Robertson - Magenta Systems Ltd wrote:
Never really looked at KeepAlive. From the naming it sounds like a means
of keeping an idle connection open, but in practice seems to be
implemented as an idle timeout, and 10 seconds is very short for such a
timeout.
I don't think so. According