Aki Niemi wrote: > the semantic is not: hmm, a notification. I know they're supposed to be > generated when state changes, but I'm not convinced the state has > changed. I better match the etag with my stored history of etags to see > whether the state *really* changed. Ha! A match! The notifier farm > must've rebooted or the Lakers indeed fired Koby! I better calculate the > nth decimal of pi, launch doom and busy-loop for the rest of the day. > > 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? -- 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
