-
About the snapshots, they come for the various items in the table independently of one another, just like the real-time updates
and there is no notification that all of them have been received.
You could determine that by knowing how many items are in the table,
but, unfortunately, the information on the number of items is indeed lacking for the SimpleTableInfo case.
Do you confirm that in your case the client, at the time of subscription, doesn't know how many items are involved?
To workaround the limitation, your Metadata Adapter, when resolving the group ID in getItems, could add a "sentinel" item as the last element of the returned array.
The sentinel item would just associate a recognizable value to a specific field, so that the client, upon reception of the snapshots, could recognize that value and take the index of the related item as the last one (still, it would be possible that the shapshot for some of the previous items would be yet to come).
-
Will LS send snapshot events without any updates in this case? Or is it possible that some update events for the items the snapshot was already sent might be slotted into the sequence?
-
All events pertaining to one item are independent with respect to events pertaining to other items, even if they are subscribed within the same table.
So, it is possible that your client receives
the snapshot for item ItemA
followed by a real-time update for item ItemA
followed by the snapshot for item itemB.
Obviously, this happens in short time, as the Server always sends the snapshots as soon as possible.
-
Thank you for the clarification.