I implemented fetching of context (manual) - my server simply reads the latest N items from the collection.
While working on that I realized that synchronization can be done differently. If context collection contains activities that modify it (such as Add and Remove), in reverse chronological order, the client can re-construct the current state by fetching them and applying one by one. There is no need to compute digests with this approach, remembering latest activity ID would be enough.
Conversation
Notices
-
silverpill (silverpill@mitra.social)'s status on Friday, 02-Aug-2024 13:53:39 JST silverpill -
silverpill (silverpill@mitra.social)'s status on Friday, 02-Aug-2024 14:25:56 JST silverpill @julian Even if context contains objects and not activities, synchronization can be done by requesting all activities where Activity.target == Object.context (from the outbox perhaps?)
-