You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -60,7 +60,7 @@ internal final class DefaultMessageReactions: MessageReactions {
60
60
61
61
// (CHA-MR6) Users must be able to subscribe to message reaction summaries via the subscribe method of the MessagesReactions object. The events emitted will be of type MessageReactionSummaryEvent.
logger.log(message:"Subscribing to message reaction summary events", level:.debug)
65
65
66
66
leteventListener= channel.subscribe{[weak self] message in
@@ -101,7 +101,7 @@ internal final class DefaultMessageReactions: MessageReactions {
101
101
102
102
// (CHA-MR7) Users must be able to subscribe to raw message reactions (as individual annotations) via the subscribeRaw method of the MessagesReactions object. The events emitted are of type MessageReactionRawEvent.
logger.log(message:"Subscribing to reaction events", level:.debug)
106
106
guard options.rawMessageReactions else{
107
107
// (CHA-MR7a) The attempt to subscribe to raw message reactions must throw an ErrorInfo with code 40000 and status code 400 if the room is not configured to support raw message reactions
logger.log(message:"Subscribing to messages", level:.debug)
41
41
// (CHA-M4c) When a realtime message with name set to message.created is received, it is translated into a message event, which contains a type field with the event type as well as a message field containing the Message Struct. This event is then broadcast to all subscribers.
42
42
// (CHA-M4d) If a realtime message with an unknown name is received, the SDK shall silently discard the message, though it may log at DEBUG or TRACE level.
@@ -34,7 +34,7 @@ internal final class DefaultRoomReactions: RoomReactions {
34
34
// (CHA-ER4) A user may subscribe to reaction events in Realtime.
35
35
// (CHA-ER4a) A user may provide a listener to subscribe to reaction events. This operation must have no side-effects in relation to room or underlying status. When a realtime message with name roomReaction is received, this message is converted into a reaction object and emitted to subscribers.
// (CHA-T10a) A grace period shall be set by the client (the grace period on the CHA-T10 heartbeat interval when receiving events). The default value shall be set to 2000ms.
// (CHA-T14) Multiple asynchronous calls to keystroke/stop typing must eventually converge to a consistent state.
16
16
// (CHA-TM14a) When a call to keystroke or stop is made, it should attempt to acquire a mutex lock.
17
17
// (CHA-TM14b) Once the lock is acquired, if another call is made to either function, the second call shall be queued and wait until it can acquire the lock before executing.
18
18
// (CHA-TM14b1) During this time, each new subsequent call to either function shall abort the previously queued call. In doing so, there shall only ever be one pending call and while the mutex is held, thus the most recent call shall "win" and execute once the mutex is released.
@@ -35,7 +35,7 @@ internal final class DefaultTyping: Typing {
35
35
36
36
// (CHA-T6) Users may subscribe to typing events – updates to a set of clientIDs that are typing. This operation, like all subscription operations, has no side-effects in relation to room lifecycle.
0 commit comments