Skip to content
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

Fix capabilities #634

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Fix capabilities #634

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
894c48c
Removed unsupported incremental backoff feature from ably capabilities
sacOO7 Feb 16, 2024
d0eafe1
Updated readme to remove unintended limitations
sacOO7 Feb 16, 2024
c33ea4e
Fallbacks is not fully supported yet in realtime
sacOO7 Feb 16, 2024
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
5 changes: 0 additions & 5 deletions .ably/capabilities.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,6 @@ compliance:
Connection:
Disconnected Retry Timeout:
Get Identifier:
Incremental Backoff:
Lifecycle Control:
Recovery:
State Events:
Expand Down Expand Up @@ -83,10 +82,6 @@ compliance:
Support Hyperlink on Request Failure:
Service:
Environment:
Fallbacks:
Hosts:
Retry Count:
Retry Timeout:
Host:
Testing:
Disable TLS:
Expand Down
14 changes: 2 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -404,24 +404,14 @@ As of release 1.2.0, the following are not implemented and will be covered in fu
### REST API

- [Push notifications admin API](https://ably.com/docs/general/push/admin) is not implemented.

- [JWT authentication](https://ably.com/docs/core-features/authentication#ably-jwt-process) is not implemented.

### Realtime API

- There is no channel `suspended` state; this means that the client will not automatically reattach to channels if a
connection becomes `suspended` and then resumes, and presence members associated with the client will not be
automatically re-entered.

- Inband reauthentication is not supported; expiring tokens will trigger a disconnection and resume of a realtime
connection.

- Realtime connection failure handling is partially implemented.

- Inband reauthentication is not supported; expiring tokens will trigger a disconnection and resume of a realtime connection.
- Realtime fallbacks not supported.
- Realtime Ping function is not implemented.

- Message Delta Compression is not implemented.

- Push Notification Target functional is not applicable for the SDK and thus not implemented.

## Support, feedback and troubleshooting
Expand Down
Loading