I am using the excellent WebSocket++ in an unusual situation: the WebSocket++ server is at a fixed physical location but most of its .NET clients run on Windows platforms that are physically mobile and suffer from intermittently poor connectivity with the server. I need to keep the connections open for a reasonable amount of time during periods of poor connectivity (reconnection is undesirable because it requires client users to log in every time a reconnection occurs). The server regularly sends messages to its clients.
During poor connectivity the server does not close the connection if it does not send any messages (after some tweaking of keep alive intervals) but it seems that if the server tries to send a message and fails, it will close the connection after 20 seconds.
Is it possible to increase this 20 second timeout?
Tim