Re: question on 'LAST-MODIFIED' property

Harrie Hazewinkel wrote:

>
> HI all,
>
> I have an implementation kind of question regarding the LAST-MODIFIED
> property. I am curious of thoughts for this property whether it
> is useful to maintain in CAP clients (or intermediate-servers that
> act as clients).

Yes, LAST-MODIFIED was part of the synchronization discussion that took
part in the requirements for CAP.

What ever CUA is going to sync with the CS will need that property in order
to tell if which possibly modified object was the last edit of that object.

SEQUENCE and DTSTAMP tell you the last that was sent by the ORGANIZER.
However those will not tell you which has the correct copy of any added 
local
attributes (VALARM components as an example).

If the CS does not change anything as seen by the CUA, then LAST-MODIFIED is
not relevant.  If the UID, SEQUENCE, and DTSTAMP are the same
in the CUA and CS, yet the LAST-MODIFIED in the CS is newer, then it means
that another CUA updated the object (such as adding local vlarrms, or 
removing them, or ...)
and the copy in the CS should be used as the latest copy for 
synchronization.

http://www.calsch.org/ietf/archives/draft-ietf-calsch-capreq-04.txt

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
[email protected]                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards