-
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
Proposal for adding full_state param to v2 sync #133
Conversation
@@ -659,6 +659,8 @@ This API also returns an ``end`` token which can be used with the event stream. | |||
|
|||
{{sync_http_api}} | |||
|
|||
{{v2_sync_http_api}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it doesn't hurt to include this in the specification. We should add a preamble explaining how v2 /sync is supposed to work at some point. But I don't think it's essential that we do that now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It needs a lot more context. Really I just threw this in so that there's a way to check how it comes out in the spec doc.
LGTM |
A hopefully-complete implementation of the full_state incremental sync, as specced at matrix-org/matrix-spec-proposals#133. This actually turns out to be a relatively simple modification to the initial sync implementation.
Implement tests for the full_state incremental sync, as specced at matrix-org/matrix-spec-proposals#133 and implemented at matrix-org/synapse#332
This seems to work well in practice, so I'm going to ship it. |
Proposal for adding full_state param to v2 sync
Turns out that, for clients like libpurple which store message history but not room state, it would be useful to provide an interface which provides the full state of a room, but only messages since the 'since' token.
This is a proposal for how it might look in the api.