Before the heartbeats start fun would do nothing but the server
would still tell the client heartbeats were enabled, leading to
issues with default client options. Now, we provide 'undefined'
instead of a start fun and the processor sends 0,0 back to the
client instead of an incorrect value.
Before the heartbeats start fun would do nothing but the server would still tell the client heartbeats were enabled, leading to issues with default client options. Now, we provide 'undefined' instead of a start fun and the processor sends 0,0 back to the client instead of an incorrect value.
Fix for https://github.com/rabbitmq/rabbitmq-web-stomp/issues/28