Our app requires that our users have most, if not all, of the data available for their channel(s) before they can begin working.
So far, we have accomplished that by comparing the number of docs the local DB has compared to what we should have. The issue with this approach is that all of the documents could have had changes made to them. If the local DB already has those docs, the load screen would not detect those changes and the user would be allowed in prematurely.
What we’re looking for is a way to look at the number of changes that need to be pulled. If we were using one-shot replication it would be simple enough to grab the latest server sequence each time that replication ended. However, we are using continuous replication and it seems like it would be bit more complicated to know exactly when to grab the latest server revision to store.
If we had some way to grab that directly from the replicator, it would be a much more simple task and I believe that it would prove useful for many developers.
Is there a specific reason as to why it is not exposed, or is it just something that hasn’t been requested until now?