Presence messages superseded whilst channel in attaching state

[AndyTWF]

presence.enter and presence.update (and the others) call presence.updatePresence.

updatePresence will put messages on a queue to be sent later, in the event that the channel is currently attaching. This queue is a HashMap that is keyed by clientid. This means if a presence.enter and presence.update occur in quick succession before the channel attaches, the former is cancelled out by the latter (and any listeners are not called).

There are two possible options:

1. Queue up all presence messages and then send in-order on channel attach.
2. Only send the latest message, but call all event listeners with the result.

The spec needs updating to provide more clarification on what the behaviour should be (see: ably/specification#130), but the current implementation in ably-js is to just send all of the pending messages.

[sync-by-unito]

➤ Automation for Jira commented:

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