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.

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

Channel attach with resume from serial #65

Open
mattheworiordan opened this issue Jul 20, 2018 · 2 comments
Open

Channel attach with resume from serial #65

mattheworiordan opened this issue Jul 20, 2018 · 2 comments

Comments

@mattheworiordan
Copy link
Member

mattheworiordan commented Jul 20, 2018

In future, when we have global time serials, customers may want to easily resume a channel from a time serial, that could for example be two days old.

In order to achieve this we'll need to consider:

  • An API to expose last time serial on a channel
  • An channel option to resume from a serial number, along with other options such as { limit: 5 } to indicate the channel should not recover a limitless number of messages. It would be useful to also have an option such as { last: 2 } to request on attach that the last two publishes messages are sent
  • An ACK mechanism from the server to the client to ensure the client is keeping up with the potentially huge stream of messages it's about to receive

┆Issue is synchronized with this Jira Task by Unito

@mattheworiordan
Copy link
Member Author

Note this is somewhat done now with Channel Rewind, although without a global time serial yet in place, and no way to inspect a serial and resume from a serial, this feature is still outstanding.

@QuintinWillison QuintinWillison transferred this issue from ably/docs Oct 3, 2022
@sync-by-unito
Copy link

sync-by-unito bot commented Oct 17, 2022

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2810

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants