[Cosmo-dev] Interesting idea to avoid EIM conflicts

[Randy Letness]

Brian Moseley wrote:
>> The server should apply them if the timestamp is newer than the
>> item's current "last modified" timestamp.  If a client sends a
>> deletion record, Cosmo just needs to be able to tell other clients
>> that the record got deleted.
>
> sounds like the server wants to respond to a deleted record by nulling
> the lastModifedBy attribute and to a non-deleted record by setting the
> attribute.
>
> will the client ever send both a deleted record and a regular record,
> or will it always just be one or the other?

Seems like Cosmo could ignore deletion records and just apply the 
regular records.  Cosmo wouldn't be able to send deletion records, just 
the most recent record.  Could Chander just implicitly delete older records?

-Randy