WebSocket Timeout

Timeouts are per connection. When a Timeout is set to 60 seconds and there is no data being sent or received through that connection for 60 seconds, a Timeout is triggerd to close the inactive connection.

If you want to completely disable Timeouts after a specific event, you can change the Timeout property for that event by setting its value to -1, or change the timeout interval by using another value. For example, if you wanted to use a 300 seconds timeout after accepting and upgrading a WebSocket connection, you could set ...

Sender.Timeout.AfterDataSent:=300;

... directly from the event where you have upgraded the connection to a WebSocket. This would change the timeout interval to 300 seconds (5 minutes) after sending the WebSocket upgrade response to the Client. Naturally, this only works if all other Timeout properties (which could trigger for the same connection afterwards) are set to 0 (default).

You could also change the timeout interval from RTC events by using the Sender.Timeout.Enable() method (check method description for details), or temporarily disable the Timeout until the next event is triggered by using the Sender.Timeout.Disable method, but ... please keep in mind that both of these methods are only temporary and will be overriden if any other event with a timeout option is triggered.

NOTE: Disabling a timeout or using very long timeout intervals does NOT give you a guarantee that a connection would NOT be closed after some time of inactivity. Especially if the Client is behind a proxy, your connections are likely to be closed if there is no data being sent or received for a while. How long a connection would stay open without any traffic depends on proxy servers and the network being used, but I wouldn't expect any connection without traffic to remain open for much loner than 30 seconds. When using WebSockets, you can send a PING frame periodically to keep your connection active. Sending a PING every 30 seconds to keep a connection active and using a 60 second timeout should work in most networks, without generating too much "noise".

Best Regards,
Danijel Tkalcec