What about enabling TCP keep-alive and timeout? ICSv7 TWSocketServer has
these properties!
Regards,
SZ
On Mon, Jan 12, 2009 at 8:13 PM, gaetan.s...@gmail.com wrote:
Hello,
I am using the TWSocketServer (Server) component to which several TWSocket
components connect (Client),
I
What about enabling TCP keep-alive and timeout?
ICSv7 TWSocketServer has these properties!
My experience is that many topologies do not work reliably using those
features. The best way is really to use an application level ping command as
I explained.
--
francois.pie...@overbyte.be
Author of
What kind of feature mechanism can you suggest for a TCP tunnel proxy then?
On Tue, Jan 13, 2009 at 12:59 PM, Francois Piette francois.pie...@skynet.be
wrote:
What about enabling TCP keep-alive and timeout?
ICSv7 TWSocketServer has these properties!
My experience is that many topologies
Hi all,
In order to make ICS better everybody can help by just testing new
features and bugfixes. Current HTTP changes in the ICS SVN repository
are:
V7 OverbyteIcsHttpProt.pas
Added Digest Access Authentication.
In order to disable this feature entirely undefine
directive
What about enabling TCP keep-alive and timeout?
ICSv7 TWSocketServer has these properties!
My experience is that many topologies do not work reliably using those
features. The best way is really to use an application level ping
command
as I explained.
What kind of feature mechanism
Hello Francois,
Well the tunnel client and server is ours but it has 4 ends.
TCPClient--Internet--TunnelSSLClient--Internet--TunnelSSLServer-Internet--TCPServer
Regards,
SZ
On Tue, Jan 13, 2009 at 5:23 PM, Francois Piette
francois.pie...@skynet.bewrote:
What about enabling TCP keep-alive
What about enabling TCP keep-alive and timeout?
ICSv7 TWSocketServer has these properties!
My experience is that many topologies do not work reliably using
those
features. The best way is really to use an application level ping
command as I explained.
What kind of
