[Cosmo-dev] detaching item occurrences
Randy Letness
randy at osafoundation.org
Fri Aug 10 09:38:42 PDT 2007
Brian Moseley wrote:
>
> the server detaches the targeted occurrence, making it a master in its
> own right. all occurrences and modifications from the original that
> occur after the detached occurrence are transferred to the new master.
> the new master is added to all collections of which the original
> master is a member.
>
So basically the client is creating a new recurring event based on the
existing event and any changes. This means the client is responsible
for creating the complete recordset for the new recurring event. By
using this special projection the server knows to modify the existing
recurring event (breaking the series at that point) and moving any
relevant modifications to the new recurring event.
-Randy
More information about the cosmo-dev
mailing list