-
Notifications
You must be signed in to change notification settings - Fork 0
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
docs: first API draft #1
Conversation
A bit of a general question - how do we see the customer application interacting with the library? Lets say I wanted to "scroll up" my chat and get some older messages - would I just do a How would huge volumes of messages be handled - lets say a user decided to scroll all the way up a chat (containing say millions of messages), would the client library try to hold every message in memory? Or would we make it some sort of sparse cache, that may not contain all messages - but is guaranteed to contain the latest version of a message if it does have it? That sorta leads me on to a thought - do we make the client library implement a "window" of messages? Like, the customer tells the library which window of messages the user is currently in, and the library only generates events for messages in that window? Thus it keeps the number of messages the library has in memory to a fixed size? |
53b1e4e
to
7c9dbc8
Compare
No description provided.