On ti, 2008-03-04 at 10:59 -0600, ext Dean Willis wrote: > Do we have a requirement to keep our history straight? Perhaps not. > After further reflection, I think that for the common use case > (keeping track of the current version of a document with full document > transmittal) the technique as proposed by Aki works just fine. Since > etags aren't really sequential, we don't really gain anything by the > ability to detect dropped cycles, do we? > > Somebody needs to think this through from the perspective of partial > notification.
In S 4: With partial event notification, the NOTIFY message only carries the delta state, or the set of changes to the previous version of the entity. In that case, implementations MUST consider the full event state as the version of the entity to which the entity-tag in the NOTIFY message applies. In other words, you're not tagging the individual deltas, but the resulting state after the delta has been applied. Cheers, Aki _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
