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
Copy file name to clipboardExpand all lines: roadmap.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,18 @@ This document outlines our plans for the evolution of this SDK.
7
7
Once we've completed the scope and objectives detailed in this milestone,
8
8
we'll be in a good position to make a release in order to start getting feedback from customers.
9
9
10
+
That release will allow applications built against it to:
11
+
12
+
- Create a persistent Realtime connection to the Ably service
13
+
- Subscribe to Ably channels in order to receive messages over that connection
14
+
15
+
That release will come with the following known limitations:
16
+
17
+
- No resilience to single Ably endpoint failure. To be implemented under [Milestone 2: Realtime Connectivity Hardening](#milestone-2-realtime-connectivity-hardening).
18
+
- No support for [Token authentication](https://ably.com/docs/core-features/authentication#token-authentication), meaning that it only supports authentication by directly using a 'raw' Ably API key ([Basic authentication](https://ably.com/docs/core-features/authentication#basic-authentication)). To be implemented under [Milestone 3: Token Authentication](#milestone-3-token-authentication).
19
+
- No capability to publish over the Realtime connection. To be implemented under [Milestone 4: Realtime Channel Publish](#milestone-4-realtime-channel-publish).
20
+
- No capability to receive or publish member presence messages for a channel over the Realtime connection. To be implemented under [Milestone 5: Realtime Channel Presence](#milestone-5-realtime-channel-presence).
21
+
10
22
### Milestone 1a: Solidify Existing Foundations
11
23
12
24
Ensure the current source code is in a good enough state to build upon.
@@ -83,10 +95,10 @@ _T.B.D. but will include environments and connection resume._
83
95
84
96
_T.B.D. but necessary in order to utilise capabilities embedded within signed JWTs for production applications._
0 commit comments