-
Notifications
You must be signed in to change notification settings - Fork 16
Confirm status of remaining realtime spec items for 1.0 #244
Description
Confirm the status (implemented or not implemented) of the following 13 spec items:
|----|
|* (RTN11b) If the state is CLOSING, the client should make a new connection with a new transport instance and remove all references to the old one. In particular, it should make sure that, when the CLOSED ProtocolMessage arrives for the old connection, it doesn’t affect the new one.|
|* (RTN11c) If the state is DISCONNECTED or SUSPENDED, aborts the retry process described in RTN14d and RTN14e and immediately tries to reconnect.|
|* (RTN11d) If the state is FAILED, transitions all the channels to INITIALIZED, sets their errorReason to null, and sets the connection’s errorReason to null.|
|* (RTN12f) If the connection state is CONNECTING, moves immediately to CLOSING. If the connection attempt succeeds, ie. a CONNECTED ProtocolMessage arrives from Ably, then do as specified in RTN12a. If it doesn’t succeed, move to CLOSED.|
|* (RTN12d) If the connection state is DISCONNECTED or SUSPENDED, aborts the retry process described in RTN14d and RTN14e and transitions the connection immediately to the CLOSED state|
|* (RTN15h) If a DISCONNECTED message is received from Ably, then that transport will subsequently be closed by Ably|
|(RTL15) Channel#properties attribute is a ChannelProperties object representing properties of the channel state. properties is a publically accessible member of the channel, but it is an experimental and unstable API. It has the following attributes:|
|* (RTL15a) attachSerial is null when the channel is instanced, and is updated with the channelSerial from each ATTACHED ProtocolMessage received from Ably with a matching channel attribute. The attachSerial value is used for untilAttach queries, see RTL10b and RTP12b.|
|* (RTL13c) If the connection is no longer CONNECTED, then the automatic attempts to re-attach the channel described in "RTL13b":#RTL13b must be cancelled as any implicit channel state changes subsequently will be covered by RTL3|
|@(RTP5b)@ If a channel enters the @attached@ state then all queued presence messages will be sent immediately. A presence @sync@ may be initiated per "@rtp1@":#RTP1|
|* (RTP6c) Implicitly attaches the Channel if the channel is in the INITIALIZED state. The optional callback, if provided, is called according to RTL4d based on the implicit attach operation. The listener will always be registered regardless of the implicit attach result|
|* (RTP10d) If the client is not currently ENTERED, Ably will respond with an ACK and the request will succeed (i.e. the outcome of asking to LEAVE when not present vs being present is the same)|
|* (TR4e) [REMOVED] connectionKey is no longer part of the 1.0 spec, deprecated, please remove|
Acceptance Criteria:
- Spreadsheet updated accordingly
- Issues created for missing spec items
┆Issue is synchronized with this Jira Story by Unito