eric280
Hello,
The LSSubscriptionDelegate includes the method `- subscription:didLoseUpdates:forItemName:itemPos:`. The documentation says: "By implementing this method it is possible to perform recovery actions." What are the recommended recovery actions?
--
Thanks,
Eric Baker
Dario Crivelli
Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.
Dario Crivelli
Let me clarify that another important case that can lead to lost updates is when the Server itself imposes a frequency limit because of licensing restrictions. In fact, this restriction also applies to items subscribed to in RAW mode or with "unfiltered" frequency specified.
In this case, you still cannot recover the issue at runtime, but you can prevent it from happening by designing the application in such a way that the limitation is taken into account.
For instance, if the limit is one update per second and you want to send up to 2 updates per second without loss, you can spread the updates on multiple items and then restore the update sequence on the client side.
