On 3/11/12 4:53 AM, "Sergey Dobrov" <[email protected]> wrote:
> Still have many questions to the XEP. > > It's needed to add some examples of notifications to be sent: > > 1. How to determine that the notification is from the past and not the > current notification? The intent is that it doesn't matter; the client should use the same code path either way; the key point is that a re-publish of a given item with the same ID replaces the previous item. If you need a timestamp on the publish, the publisher should add it into the payload. > 2. Will the server send retracts or node configuration changes > notifications from the past? Yes. Perhaps we need to call out that a node could always send a purge notification, then re-publish all current items if there are too many changes to track. > Possibly, this "ago" payload should be included in presence > automatically by server since it's not always possible to determine the > value on the client side (I already gave an example when other resource > is becoming online with higher priority and then other resources can't > receive events in case of pubsub and not presence subscription). This is about the age of the cache on the client side, so the server doesn't have the information. If it's a different client, it will have a different value. > Another still uncovered thing is how to determine missed notifications > in the case of connection failures. This is really an implementation detail of how the client sets the time in the ago. -- Joe Hildebrand
