It can take the server sometime to initially send a message to the client, as the server only sends a heartbeat every 5 seconds, but the client may (and will if no heartbeat received) cancel the client-event connection and create a new one ever 1 second. It is possible to be in a not-talking-to-each-other loop for some time (the worst I have seen/measured was upwards of 60 seconds). This update forces the server to send an initial heartbeat immediately thus reducing the the client constantly cancelling and reconnecting.
Description
It can take the server sometime to initially send a message to the client, as the server only sends a heartbeat every 5 seconds, but the client may (and will if no heartbeat received) cancel the client-event connection and create a new one ever 1 second. It is possible to be in a not-talking-to-each-other loop for some time (the worst I have seen/measured was upwards of 60 seconds). This update forces the server to send an initial heartbeat immediately thus reducing the the client constantly cancelling and reconnecting.
Resolves #(issue)