Replaced ping setInterval integration with webworker

[tomamatics]

The use of setInterval can be paused by the OS as soon as the browser tab or mobile browser app is in the background. Due to this behavior, the Stomp client library no longer sends ping messages and the Stomp server will close the connection. By using a webworker, the affected code will continue to run and ping-messages will be sent, even if the tab/app is not active.

[kum-deepak]

This does look interesting and useful. A couple of feedback:

• Looking at the automated runs, this scheme does not work on NodeJS.
• We can add checks if WebWorkers are available and use the new behavior accordingly.
• In addition, we can introduce a flag to control this behavior.

Please only commit changes to the src folder. Makes it easier to review and compare.

[kum-deepak]

Many thanks! The code looks beautiful. Please allow me a few days to review this.

I may have a few suggestions - those will be optional. In addition, if possible, we should figure out to include it as part of the tests as well.

[tomamatics]

Thanks for the review. Again, i fixed some minor issues. Tests should be running now.

[kum-deepak]

Will release as pert of v7.1

[drando]

Hi! sorry to ask, do you have an estimated ETA for v7.1? can't find that info, and this would be great to finally resolve the issue about timers throttled in chrome. Thanks!

[ianninirojas]

Hi, does anyone know when v7.1 will be released. Sorry if this question makes anyone uncomfortable. Greetings.

[ghost]

Please refrain from asking for the release (and for anything else for that matter), as it will:

1. Spam everybody's inbox that subscribed to this ticket
2. Does not help in releasing this faster to the public
3. Is straight up annoying

[mikadev]

I think this is not a good solution to add webworker, rememeber webworker will be created for each tab.
By the way this is not a bug like a lot of users reported.
The browser can pause js after a few time, so yes the heartbeat from the client are not sended but most of the time, this is not really useful to send hearbeat from the client side.
Only from the server side to keep the connection open (for the server without adding a long connection timeout) so i suggest to configure both client and server side to only send hearbeat from the server.