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

sending messages ID to client API #243

Open
flohoch opened this issue May 3, 2023 · 0 comments
Open

sending messages ID to client API #243

flohoch opened this issue May 3, 2023 · 0 comments
Labels
enhancement New feature or request priority:low

Comments

@flohoch
Copy link
Contributor

flohoch commented May 3, 2023

The clients (android & iOS) save the IDs of read messages, thus it might be a more optimized way to send the ID of the last read message to the OnLaunch server which responds with messages with IDs higher than the last read message ID. In case there are currently active blocking messages with a smaller ID, they have to be sent as well.

Check if this approach is feasible and a good idea in general. Possibly implication might be a problem when it comes to manually change the order of message in the frontend. Or in general, when e.g. the server sorts by start and end dates and messaged IDs get shuffled (i.e. ID 13 comes before 7, if 13 is flagged as read, but 7 is not, the next time 7 would not be loaded)

@flohoch flohoch added enhancement New feature or request priority:low labels May 3, 2023
@flohoch flohoch self-assigned this May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:low
Projects
None yet
Development

No branches or pull requests

1 participant