Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Paginated Sync #893

Closed
wants to merge 43 commits into from
Closed

Paginated Sync #893

wants to merge 43 commits into from

Conversation

erikjohnston
Copy link
Member

No description provided.


missing_list = frozenset(
room_id for room_id, ts in
sorted(start_ts.items(), key=lambda item: -item[1])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why sorted?

@pik
Copy link
Contributor

pik commented Jan 3, 2017

What's the status on this? Is there a summary of the issues / intended or even a log of the discussion around somewhere?

Probably related: element-hq/element-web#2825 element-hq/element-web#2737

@@ -690,6 +791,12 @@ def _generate_sync_entry_for_rooms(self, sync_result_builder, account_data_by_ro

tags_by_room = yield self.store.get_tags_for_user(user_id)

yield self._update_room_entries_for_paginated_sync(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be missing something - but I don't think this is sufficient or an effective way to breakdown sync - since which room is synced is still not granular. The client should really be able to specify which room should be synced first, otherwise it's going to waste time syncing rooms which the user might not be currently interested in, no?

@erikjohnston
Copy link
Member Author

This is not going to happen because there is no one on the client side available to test it out.

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

Successfully merging this pull request may close these issues.

3 participants