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

Decentralization Client: Persist the "last_seen" cursor per group #1545

Open
mkysel opened this issue Jan 24, 2025 · 0 comments
Open

Decentralization Client: Persist the "last_seen" cursor per group #1545

mkysel opened this issue Jan 24, 2025 · 0 comments
Labels

Comments

@mkysel
Copy link
Contributor

mkysel commented Jan 24, 2025

Is your feature request related to a problem?

This is a sticky topic and I am proposing one possible solution. This is by no means the best or the final.

Groups can be synchronized independently from each other. In ideal conditions, all groups will have exactly the same cursor, which is the same "last_seen" as the one used by the main stream.

Upon restart or reconnect, a new stream can be opened with exactly the same last_seen as last time and no messages will get missed.

Realistically this might not work in the real world in all cases.

We have been talking about clients that have 1000s of groups or clients who's network capacity can't keep up with the message stream.

It is feasible to assume that the client might want to sync the most important (or last seen, or most recently messaged) groups first and then batch the remaining 1000s in some slower pipe.

Solutions like these would lead to a world in which each group has a different last_seen cursor.

At a bare minimum, this feature is required for #1544 / #1543

Describe the solution to the problem

No response

Describe the uses cases for the feature

No response

Additional details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

1 participant