-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Guaranteed delivery and LiveQuery #2077
Comments
My recommendation is to issue a regular query for objects updated after the time the app got suspended, and before it resumed. Guaranteed delivery would certainly be useful, but is a difficult problem to solve, and isn't on our roadmap. |
Thanks for your suggestion @drew-gross. I can see how this approach would identify added / modified Parse objects during the time interval. Is there a way to construct a query to identify Parse objects that were deleted during the interval? |
No, since the data is gone from the DB. One thing you could do in that case is to "soft-delete" object, by setting a "deleted=true" flag on them, then processing updates that set "deleted=true" as if they were deletes. |
Thanks @drew-gross. That's a good suggestion. |
In considering LiveQuery for my React Native app, it would be highly useful if the LiveQuery Server maintained an undelivered message Queue. That way, when my app resumes from suspended state, it can re-connect with LiveQuery Server and receive pending query results.
Has this "guaranteed delivery" use-case been discussed at all?
The text was updated successfully, but these errors were encountered: