Closed
Description
Hyperstack.send_to_server will cleanly drop messages on the floor if the server is not up, but relies on getting back an HTTP error code (i.e. 504). There are cases that due to setup problems with the server unrelated to Hyperstack, the request to the server may simply hang.
This causes Hyperstack.send_to_server to propagate a timeout error back up the system, which crashes the whole console (for example.)
This makes debugging the unrelated server problem difficult.
What we need to do is wrap send_to_server in a configurable timeout that will cleanly drop the message.
While we are at it, setting the configurable timeout to a negative value should simply drop the value, while 0 and nil should ignore the time out.