You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was just wondering if you use a subscription cache for paging through documents using a skip, limit, and sort, for example, as you page through the documents, those documents will get retained and build up in minimongo on the client.
You'll then need to update your client code to paginate through them correctly. Where with just using regular pub/sub you only have the current page of documents on the client, so you code can just return the currently published set of documents (which is really the current page).
If you update your client code to pass skip, limit, and sort to a minimongo query, in order to retrieve the correct page of documents from all the cached documents, what happens when the cached subscriptions expire in the middle of all this?
Seems like that would throw a wrench into everything... like sand shifting underneath your minimongo code.
The text was updated successfully, but these errors were encountered:
Was just wondering if you use a subscription cache for paging through documents using a
skip
,limit
, andsort
, for example, as you page through the documents, those documents will get retained and build up in minimongo on the client.You'll then need to update your client code to paginate through them correctly. Where with just using regular pub/sub you only have the current page of documents on the client, so you code can just return the currently published set of documents (which is really the current page).
If you update your client code to pass
skip
,limit
, andsort
to a minimongo query, in order to retrieve the correct page of documents from all the cached documents, what happens when the cached subscriptions expire in the middle of all this?Seems like that would throw a wrench into everything... like sand shifting underneath your minimongo code.
The text was updated successfully, but these errors were encountered: