Check connection health using HEARTBEAT

[sacOO7]

• Check if the connection is still active using the PING-PONG mechanism
• It seems there are possible CONNECTION LEAKS, which can avoid emitting DISCONNECTED event, hence increasing queueSize for published messages ( client will keep publishing messages on LEAKED/OPEN connection )
• One of the temp. patch applied for the same -> https://gist.github.com/marto83/17be1a0f8d99b76442b17c265e8687e0
• This still created a problem -> https://ably-real-time.slack.com/archives/C0174D4AP4P/p1667835754601099
• Main aim is to identify if HEARTBEAT SPEC is properly implemented, and use it to identify CONNECTION HEALTH
• This will help get rid of temporary/poorly designed workarounds for handling connection leaks.

┆Issue is synchronized with this Jira Task by Unito

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2905