-
Notifications
You must be signed in to change notification settings - Fork 385
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
Unclear how to determine boundaries of backlog in /sync API? #2849
Comments
In this example, there are two /sync requests: the first returned events up to A, and a next_batch token: let's call it You are looking to fill the gap between I think you know this though, because you've implied you've tried it at #2251 (comment). So, is this just a duplicate of #2251? |
The spec doesn't support passing sync tokens into |
True. That's #2420. |
I can't understand why this isn't a duplicate of #2251. |
When using
/sync
, it's possible to receive alimited
response with aprev_batch
token, which can be used with/messages
to fetch the omitted backlog. So far, so good.However, how do I know whether I've reached the end of that omitted backlog?
For example: say that I do a sync "since A", and I receive a limited response of D,E,F, so B and C are omitted. When following the included continuation token, how do I know that I've received C and B, therefore reached the end of that backlog, and there's nothing more to obtain - so that I don't duplicate processing of event A?
I've been unable to find a clear answer to this in the spec, and asking in #matrix-dev also yielded no answers.
The text was updated successfully, but these errors were encountered: