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
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
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.
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:
{ 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┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: