Skip to content

fix spec point missed in markdown conversion #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
owenpearson wants to merge 1 commit into from
Closed

fix spec point missed in markdown conversion #439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions specifications/features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -853,8 +853,8 @@ The threading and/or asynchronous model for each realtime library will vary by l
- `(RTP17h)` Unlike the main `PresenceMap`, which is keyed by [memberKey](#TP3h) , the `RTP17` `PresenceMap` must be keyed only by `clientId`. (Otherwise, entries associated with old `connectionId`s would never be removed, even if the user deliberately leaves presence).
- `(RTP17f)` This clause has been replaced by [`RTP17i`](#RTP17i). It was valid up to and including specification version `3.0`.
- `(RTP17i)` The `RealtimePresence` object should perform automatic re-entry whenever the channel receives an `ATTACHED` `ProtocolMessage`, except in the case where the channel is already attached and the `ProtocolMessage` has the `RESUMED` bit flag set.
- `(RTP17g)` Automatic re-entry consists of, for each member of the `RTP17` internal `PresenceMap`, publishing a `PresenceMessage` with an `ENTER` action using the `clientId`, `data`, and `id` (subject to `RTP17g1) attributes from that member.
*** `(RTP17g1)@ If the current connection `id` is different from the `connectionId` attribute of the stored member, the published `PresenceMessage` must not have its `id` set.
- `(RTP17g)` Automatic re-entry consists of, for each member of the `RTP17` internal `PresenceMap`, publishing a `PresenceMessage` with an `ENTER` action using the `clientId`, `data`, and `id` (subject to [`RTP17g1`](#RTP17g1)) attributes from that member.
- `(RTP17g1)` If the current connection `id` is different from the `connectionId` attribute of the stored member, the published `PresenceMessage` must not have its `id` set.
- `(RTP17c)` This clause has been replaced by [`RTP17f`](#RTP17f). It was valid up to and including specification version `1.2`.
- `(RTP17c1)` This clause has been deleted. It was valid up to and including specification version `1.2`.
- `(RTP17c2)` This clause has been deleted. It was valid up to and including specification version `1.2`.
Expand Down
Loading