[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fw: Correct handling of Recurrence-id





Bruce_Kahn@xxxxxxxxxxxxxxxx wrote:

Doug repined on 06/18/2003 03:54:17 PM: > There is a way to re-map, tie the sequence number to the recurrence-id. > OR when they do not map, do a REFRESH. Any CUA needs to be able > to do a REFRESH anyway if things get out of sync for any reason > including recurrence-id issues.

SHOW ME HOW A REFRESH IN A DELTA MODEL WORKS! If you miss 1 reschedule you cannot ever recover no matter what voodoo you _THINK_ or _CLAIM_ happens. Show us otherwise! Ive already demonstrated how it fails but perhaps your Kung Fu is stronger. Show us...

So Bruce, what do YOU expect to get back from a REFRESH? An unrelated object? A another UID object? Or a voodoo doll :-) Or the entire object you asked for?

I really do not understand why you think that a REFRESH will
not get you the object you ask be sent.

You have not shown any examples of how a REFRESH returns bogus data.
You have not shown any examples of how the results of a REFRESH
are anything un-usable.

If you do a REFRESH on UID:1, you get back the UID:1 object
in its latest and most up to date state.



 Doug Royer                     |   http://INET-Consulting.com
 -------------------------------|-----------------------------
 Doug@xxxxxxxxx                 | Office: (208)612-INET
 http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                |   Cell: (208)520-4044

We Do Standards - You Need Standards

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature