Snapshots about matrix-client-api HOT 2 OPEN

Since we can't guarantee that there will be no other event between the "trigger event" and the snapshot event the snapshot needs to refer to the trigger event. That way one can check for additional events and apply them accordingly.

io.syncpoint.odin.chunk = {
  content: {{BASE_64_ENCODED_CONTENT}}
}

io.syncpoint.odin.snapshot = {
  trigger: {{event_id_of_the_trigger_event}},
  chunks: [
    {{chunks_event_id_0}},  // typeof io.syncpoint.odin.chunk
    {{chunks_event_id_1}},
    {{chunks_event_id_2}},
    {{chunks_event_id_n}},
  ]
}

from matrix-client-api.

The snapshot is the most recent state and does not contain any del operations. Applying the snapshot means removing all items that are NOT part of the snapshot or the subsequents events.

from matrix-client-api.