Skip to content

Commit cdb9d58

Browse files
committed
Add separate page for Objects spec, RealtimeChannel.objects and OBJECT_SYNC spec
1 parent ccc5329 commit cdb9d58

3 files changed

Lines changed: 140 additions & 3 deletions

File tree

scripts/find-duplicate-spec-items

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
# Script to detect duplicate spec IDs in the client library spec
44
# This tends to happen when concurrent spec PRs are merged
55

6-
SPEC_FILES = ["features", "chat-features"]
6+
SPEC_FILES = ["features", "chat-features", "objects-features"]
77

88
has_errors = false
99

textile/features.textile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -680,7 +680,7 @@ h3(#realtime-channels). Channels
680680
h3(#realtime-channel). RealtimeChannel
681681

682682
* @(RTL23)@ @RealtimeChannel#name@ attribute is a string containing the channel’s name
683-
* @(RTL1)@ As soon as a @RealtimeChannel@ becomes attached, all incoming messages and presence messages (where 'incoming' is defined as 'received from Ably over the realtime transport') are processed and emitted where applicable. @PRESENCE@ and @SYNC@ messages are passed to the @RealtimePresence@ object ensuring it maintains a map of current members on a channel in realtime
683+
* @(RTL1)@ As soon as a @RealtimeChannel@ becomes attached, all incoming messages, presence messages and object messages (where 'incoming' is defined as 'received from Ably over the realtime transport') are processed and emitted where applicable. @PRESENCE@ and @SYNC@ messages are passed to the @RealtimePresence@ object ensuring it maintains a map of current members on a channel in realtime. @OBJECT@ and @OBJECT_SYNC@ messages are passed to the @Objects@ object ensuring it maintains an up-to-date representation of objects on a channel in realtime
684684
* @(RTL2)@ The @RealtimeChannel@ implements @EventEmitter@ and emits @ChannelEvent@ events, where a @ChannelEvent@ is either a @ChannelState@ or @UPDATE@, and a @ChannelState@ is either @INITIALIZED@, @ATTACHING@, @ATTACHED@, @DETACHING@, @DETACHED@, @SUSPENDED@ and @FAILED@
685685
** @(RTL2a)@ It emits a @ChannelState@ @ChannelEvent@ for every channel state change
686686
** @(RTL2g)@ It emits an @UPDATE@ @ChannelEvent@ for changes to channel conditions for which the @ChannelState@ (e.g. @ATTACHED@) does not change, unless explicitly prevented by a more specific condition (see "RTL12":#RTL12). (The library must never emit a @ChannelState@ @ChannelEvent@ for a state equal to the previous state)
@@ -937,7 +937,7 @@ then the @enter@ request results in an error immediately.
937937

938938
h3(#realtime-objects). RealtimeObjects
939939

940-
Reserved for @RealtimeObjects@ feature specification. Reserved spec points: @RTO@, @RTLO@, @RTLC@, @RTLM@
940+
Reserved for @RealtimeObjects@ feature specification, see "objects-features":../objects-features. Reserved spec points: @RTO@, @RTLO@, @RTLC@, @RTLM@
941941

942942
h3(#realtime-annotations). RealtimeAnnotations
943943

textile/objects-features.textile

Lines changed: 137 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,137 @@
1+
---
2+
title: Objects Features
3+
section: client-lib-development-guide
4+
index: 65
5+
jump_to:
6+
Help with:
7+
- Objects Features Overview#overview
8+
---
9+
10+
h2(#overview). Overview
11+
12+
This document outlines the feature specification for the Objects feature of the Realtime system. It is currently under development and stored separately from the main specification to simplify the initial implementation of the feature in other SDKs. Once completed, it will be moved to the main "features":../features spec.
13+
14+
Objects feature enables clients to store shared data as "objects" on a channel. When an object is updated, changes are automatically propagated to all subscribed clients in realtime, ensuring each client always sees the latest state.
15+
16+
h3(#realtime-objects). RealtimeObjects
17+
18+
* @(RTO1)@ @Objects#getRoot@ function:
19+
** @(RTO1a)@ Returns an object with id @root@ from the internal @ObjectsPool@ as a @LiveMap@
20+
* @(RTO2)@ Various object operations may require a specific channel mode to be set on a channel in order to be performed. If a specific channel mode is required by an operation, then:
21+
** @(RTO2a)@ If the channel is in the @ATTACHED@ state, the presence of the required channel mode is checked against the set of channel modes granted by the server per "RTL4m":../features#RTL4m :
22+
*** @(RTO2a1)@ If the channel mode is in the set, the operation is allowed
23+
*** @(RTO2a2)@ If the channel mode is missing, the library should indicate an error with code 40024 stating that the operation cannot be performed without the required channel mode
24+
** @(RTO2b)@ Otherwise, a best-effort attempt is made, and the channel mode is checked against the set of channel modes requested by the user per "TB2d":../features#TB2d :
25+
*** @(RTO2b1)@ If the channel mode is in the set, the operation is allowed
26+
*** @(RTO2b2)@ If the channel mode is missing, the library should indicate an error with code 40024 stating that the operation cannot be performed without the required channel mode
27+
* @(RTO3)@ An internal @ObjectsPool@ should be used to maintain the list of objects present on a channel.
28+
** @(RTO3a)@ @ObjectsPool@ is a @Dict<String, LiveObject>@ - a map of @LiveObject@s keyed by "@objectId@":../features#OST2a string
29+
** @(RTO3b)@ It must always be populated with a @LiveMap@ object with id @root@
30+
* @(RTO4)@ When a channel @ATTACHED@ @ProtocolMessage@ is received, the @ProtocolMessage@ may contain a @HAS_OBJECTS@ bit flag indicating that it will perform an objects sync, see "TR3":../features#TR3 . Note that this does not imply that objects are definitely present on the channel, only that there may be; the @OBJECT_SYNC@ message may be empty.
31+
** @(RTO4a)@ If the @HAS_OBJECTS@ flag is 1, the server will shortly perform an @OBJECT_SYNC@ sequence as described in "RTO5":#RTO5
32+
** @(RTO4b)@ If the @HAS_OBJECTS@ flag is 0 or there is no @flags@ field, the internal @ObjectsPool@ should be considered in sync immediately, with only one member present: a zero-value @LiveMap@ (per "RTLM4":#RTLM4) object with id @root@
33+
* @(RTO5)@ The realtime system reserves the right to initiate an objects sync of the objects on a channel at any point once a channel is attached. A server initiated objects sync provides Ably with a means to send a complete list of objects present on the channel at any point
34+
** @(RTO5a)@ When an @OBJECT_SYNC@ @ProtocolMessage@ is received with a @channel@ attribute matching the channel name, the client library must parse the @channelSerial@ attribute:
35+
*** @(RTO5a1)@ The @channelSerial@ is used as the sync cursor and is a two-part identifier: @<sequence id>:<cursor value>@
36+
*** @(RTO5a2)@ If a new sequence id is sent from Ably, the client library must treat it as the start of a new objects sync sequence, and any previous in-flight sync must be discarded:
37+
**** @(RTO5a2a)@ The current @SyncObjectsPool@ list must be emptied
38+
*** @(RTO5a3)@ If the sequence id matches the previously received sequence id, the client library should continue the sync process
39+
*** @(RTO5a4)@ The objects sync sequence for that sequence identifier is considered complete once the cursor is empty; that is when the @channelSerial@ looks like @<sequence id>:@
40+
*** @(RTO5a5)@ An @OBJECT_SYNC@ may also be sent with no @channelSerial@ attribute. In this case, the sync data is entirely contained within the @ProtocolMessage@
41+
** @(RTO5b)@ All incoming @ObjectMessage.object@ objects must be temporarily stored in the internal @SyncObjectsPool@ list during the sync sequence
42+
** @(RTO5c)@ When the objects sync has completed as per "RTO5a4":#RTO5a4, the client library must perform the following actions in order:
43+
*** @(RTO5c1)@ For each @ObjectState@ member in the @SyncObjectsPool@ list:
44+
**** @(RTO5c1a)@ If an object with @ObjectState.objectId@ exists in the internal @ObjectsPool@:
45+
***** @(RTO5c1a1)@ Override the internal data for the object as per "RTLC6":#RTLC6, "RTLM6":#RTLM6
46+
**** @(RTO5c1b)@ If an object with @ObjectState.objectId@ does not exist in the internal @ObjectsPool@:
47+
***** @(RTO5c1b1)@ Create a new @LiveObject@ using the data from @ObjectState@ and add it to the internal @ObjectsPool@:
48+
****** @(RTO5c1b1a)@ If @ObjectState.counter@ is present, create a zero-value @LiveCounter@ (per "RTLC4":#RTLC4) and override its internal data using the current @ObjectState@ per "RTLC6":#RTLC6
49+
****** @(RTO5c1b1b)@ If @ObjectState.map@ is present, create a zero-value @LiveMap@ (per "RTLM4":#RTLM4) and override its internal data using the current @ObjectState@ per "RTLM6":#RTLM6
50+
****** @(RTO5c1b1c)@ Otherwise, log a warning that an unsupported object state message has been received, and discard the current @ObjectState@ without taking any action
51+
*** @(RTO5c2)@ Remove any objects from the internal @ObjectsPool@ for which @objectId@s were not received during the sync sequence
52+
*** @(RTO5c3)@ Clear any stored sync sequence identifiers and cursor values
53+
*** @(RTO5c4)@ The @SyncObjectsPool@ must be emptied
54+
* @(RTO6)@ When needed, a zero-value object can be created if it does not exist in the internal @ObjectsPool@ for an @objectId@, in the following way:
55+
** @(RTO6a)@ If an object with @objectId@ exists in @ObjectsPool@, do not create a new object
56+
** @(RTO6b)@ The expected type of the object can be inferred from the provided @objectId@:
57+
*** @(RTO6b1)@ Split the @objectId@ (formatted as @type:hash&#64;timestamp@) on the separator @:@ and parse the first part as the type string
58+
*** @(RTO6b2)@ If the parsed type is @map@, create a zero-value @LiveMap@ per "RTLM4":#RTLM4 in the @ObjectsPool@
59+
*** @(RTO6b3)@ If the parsed type is @counter@, create a zero-value @LiveCounter@ per "RTLC4":#RTLC4 in the @ObjectsPool@
60+
61+
h3(#livecounter). LiveCounter
62+
63+
* @(RTLC1)@ The @LiveCounter@ extends @LiveObject@
64+
* @(RTLC2)@ Represents the counter object type for Object IDs of type @counter@
65+
* @(RTLC3)@ Holds a 64-bit floating-point number as a private @data@
66+
* @(RTLC4)@ The zero-value @LiveCounter@ is a @LiveCounter@ with @data@ set to 0
67+
* @(RTLC5)@ @LiveCounter#value@ function:
68+
** @(RTLC5a)@ Requires the @OBJECT_SUBSCRIBE@ channel mode to be granted per "RTO2":#RTO2
69+
** @(RTLC5b)@ If the channel is in the @DETACHED@ or @FAILED@ state, the library should indicate an error with code 90001
70+
** @(RTLC5c)@ Returns the current @data@ value
71+
* @(RTLC6)@ @LiveCounter@'s internal @data@ can be overridden with the provided @ObjectState@ in the following way:
72+
** @(RTLC6a)@ Replace the private @siteTimeserials@ of the @LiveCounter@ with the value from @ObjectState.siteTimeserials@
73+
** @(RTLC6b)@ Set the private flag @createOperationIsMerged@ to @false@
74+
** @(RTLC6c)@ Set @data@ to the value of @ObjectState.counter.count@, or to 0 if it does not exist
75+
** @(RTLC6d)@ If @ObjectState.createOp@ is present:
76+
*** @(RTLC6d1)@ Add @ObjectState.createOp.counter.count@ to @data@, if it exists
77+
*** @(RTLC6d2)@ Set the private flag @createOperationIsMerged@ to @true@
78+
79+
h3(#livemap). LiveMap
80+
81+
* @(RTLM1)@ The @LiveMap@ extends @LiveObject@
82+
* @(RTLM2)@ Represents the map object type for Object IDs of type @map@
83+
* @(RTLM3)@ Holds a @Dict<String, MapEntry>@ as a private @data@ map
84+
* @(RTLM4)@ The zero-value @LiveMap@ is a @LiveMap@ with @data@ set to an empty map
85+
* @(RTLM5)@ @LiveMap#get@ function:
86+
** @(RTLM5a)@ Accepts a key of type String
87+
** @(RTLM5b)@ Requires the @OBJECT_SUBSCRIBE@ channel mode to be granted per "RTO2":#RTO2
88+
** @(RTLM5c)@ If the channel is in the @DETACHED@ or @FAILED@ state, the library should indicate an error with code 90001
89+
** @(RTLM5d)@ Returns the value from the current @data@ at the specified key, as follows:
90+
*** @(RTLM5d1)@ If no @MapEntry@ exists at the key, return undefined/null
91+
*** @(RTLM5d2)@ If a @MapEntry@ exists at the key:
92+
**** @(RTLM5d2a)@ If @MapEntry.tombstone@ is @true@, return undefined/null
93+
**** @(RTLM5d2b)@ If @MapEntry.boolean@ exists, return it
94+
**** @(RTLM5d2c)@ If @MapEntry.bytes@ exists, return it
95+
**** @(RTLM5d2d)@ If @MapEntry.number@ exists, return it
96+
**** @(RTLM5d2e)@ If @MapEntry.string@ exists, return it
97+
**** @(RTLM5d2f)@ If @MapEntry.objectId@ exists, get the object stored at that @objectId@ from the internal @ObjectsPool@:
98+
***** @(RTLM5d2f1)@ If an object with id @objectId@ does not exist, return undefined/null
99+
***** @(RTLM5d2f2)@ If an object with id @objectId@ exists, return it
100+
**** @(RTLM5d2g)@ Otherwise, return undefined/null
101+
* @(RTLM6)@ @LiveMap@ internal @data@ can be overridden with the provided @ObjectState@ in the following way:
102+
** @(RTLM6a)@ Replace the private @siteTimeserials@ of the @LiveMap@ with the value from @ObjectState.siteTimeserials@
103+
** @(RTLM6b)@ Set the private flag @createOperationIsMerged@ to @false@
104+
** @(RTLM6c)@ Set @data@ to @ObjectState.map.entries@, or to an empty map if it does not exist
105+
** @(RTLM6d)@ If @ObjectState.createOp@ is present:
106+
*** @(RTLM6d1)@ For each key–@MapEntry@ pair in @ObjectState.createOp.map.entries@:
107+
**** @(RTLM6d1a)@ If @MapEntry.tombstone@ is @false@, apply the @MAP_SET@ operation to the specified key using @MapEntry.timeserial@ and @MapEntry.data@ per "RTLM7":#RTLM7
108+
**** @(RTLM6d1b)@ If @MapEntry.tombstone@ is @true@, apply the @MAP_REMOVE@ operation to the specified key using @MapEntry.timeserial@ per "RTLM8":#RTLM8
109+
*** @(RTLM6d2)@ Set the private flag @createOperationIsMerged@ to @true@
110+
* @(RTLM7)@ @MAP_SET@ operation for a key can be applied to a @LiveMap@ in the following way:
111+
** @(RTLM7a)@ If an entry exists in the private @data@ for the specified key:
112+
*** @(RTLM7a1)@ If the operation cannot be applied as per "RTLM9":#RTLM9, discard the operation without taking any action
113+
*** @(RTLM7a2)@ Otherwise, apply the operation:
114+
**** @(RTLM7a2a)@ Set @MapEntry.data@ to the @ObjectData@ from the operation
115+
**** @(RTLM7a2b)@ Set @MapEntry.timeserial@ to the operation's serial
116+
**** @(RTLM7a2c)@ Set @MapEntry.tombstone@ to @false@
117+
** @(RTLM7b)@ If an entry does not exist in the private @data@ for the specified key:
118+
*** @(RTLM7b1)@ Create a new entry in @data@ for the specified key with the provided @ObjectData@ and the operation's serial
119+
*** @(RTLM7b2)@ Set @MapEntry.tombstone@ for the new entry to @false@
120+
** @(RTLM7c)@ If the operation has a non-empty @ObjectData.objectId@ attribute:
121+
*** @(RTLM7c1)@ Create a zero-value @LiveObject@ in the internal @ObjectsPool@ per "RTO6":#RTO6
122+
* @(RTLM8)@ @MAP_REMOVE@ operation for a key can be applied to a @LiveMap@ in the following way:
123+
** @(RTLM8a)@ If an entry exists in the private @data@ for the specified key:
124+
*** @(RTLM8a1)@ If the operation cannot be applied as per "RTLM9":#RTLM9, discard the operation without taking any action
125+
*** @(RTLM8a2)@ Otherwise, apply the operation:
126+
**** @(RTLM8a2a)@ Set @MapEntry.data@ to undefined/null
127+
**** @(RTLM8a2b)@ Set @MapEntry.timeserial@ to the operation's serial
128+
**** @(RTLM8a2c)@ Set @MapEntry.tombstone@ to @true@
129+
** @(RTLM8b)@ If an entry does not exist in the private @data@ for the specified key:
130+
*** @(RTLM8b1)@ Create a new entry in @data@ for the specified key, with @MapEntry.data@ set to undefined/null and the operation's serial
131+
*** @(RTLM8b2)@ Set @MapEntry.tombstone@ for the new entry to @true@
132+
* @(RTLM9)@ Whether a map operation can be applied to a map entry is determined as follows:
133+
** @(RTLM9a)@ For a @LiveMap@ using @LWW@ (Last-Write-Wins) CRDT semantics, the operation must only be applied if its serial is strictly greater ("after") than the entry's serial when compared lexicographically
134+
** @(RTLM9b)@ If both the entry serial and the operation serial are null or empty strings, they are treated as the "earliest possible" serials and considered "equal", so the operation must not be applied
135+
** @(RTLM9c)@ If only the entry serial exists, the missing operation serial is considered lower than the existing entry serial, so the operation must not be applied
136+
** @(RTLM9d)@ If only the operation serial exists, it is considered greater than the missing entry serial, so the operation can be applied
137+
** @(RTLM9e)@ If both serials exist, compare them lexicographically and allow operation to be applied only if the operation's serial is greater than the entry's serial

0 commit comments

Comments
 (0)