On Mar 7, 2008, at 12:53 AM, Aki Niemi wrote: > > On to, 2008-03-06 at 12:09 -0600, ext Dean Willis wrote: >>> There *really* is no comparison done; the subscriber throws away >>> the old >>> state when a NOTIFY is received, and stores the new state. (In the >>> case >>> of partial notification, there's also patching done, but still no >>> comparison of etags). >> >> So if a changed etag doesn't mean the content changed, what the >> heck are >> we sending an etag for? > > We're sending it so that the next time the subscriber sends a > SUBSCRIBE, > it can say: "Here's the last entity I've seen. Suppress-If-Match, > please".
But in the case we're discussing, the last entity the subscriber has seen is not the last entity that that the server has seen. And the entity that the subscriber currently has isn't the same entity that the server has -- it's another entity that just happens to have the same etag as the entity that the subscriber currently has. That's a close enough match for some purposes (perhaps all of our purposes), but it's not the same thing. -- Dean _______________________________________________ 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
