Topic header

[p1gp1g]

A topic header has been introduced with 1d104b8.

A Topic header means the push server keeps only the last push message for this topic. So if the servers sends a push message for a removed event, then another push message for a new event while the device is disconnected, the device will not be aware of the removed event at reconnection.

Is that intended ?

[JonathanTreffler]

Yes, that is currently intended, but might get removed again from the spec to simplify it.
Currently this works well, because the push message does not contain information about what changed, so as long as 1 push message makes it to the client after n changes there is not problem, because the sync will fetch all changes. But the spec (not this implementation yet) now also covers calendar metadata (displayname, color) changes, where that deduplication could be a problem, if a newer metadata change notifications "covers up" a previous content change notification.

[p1gp1g]

Thanks for the answer ! All of this makes sense 👍 I'm closing it to not pollute your issues