The current method for scrolling back consists of receiving an event backlog (50 events or so) and checking to see if it has any relevant messages in it. If it does, another sync request is sent to look for additional events. I've encountered issues where there appears to be a blank document, but quite a lot was returned in the sync request, indicating that the document events might have been drowned out. This is more or less the same issue as #6, but I thought I'd mention it in case anybody opens a blank document. I had a feeling this would be a problem on busier servers, but I was more focused on fixing the core algo. sigh
The current method for scrolling back consists of receiving an event backlog (50 events or so) and checking to see if it has any relevant messages in it. If it does, another sync request is sent to look for additional events. I've encountered issues where there appears to be a blank document, but quite a lot was returned in the sync request, indicating that the document events might have been drowned out. This is more or less the same issue as #6, but I thought I'd mention it in case anybody opens a blank document. I had a feeling this would be a problem on busier servers, but I was more focused on fixing the core algo. sigh