[Cosmo-dev] This and Future issues

[Brian Moseley]

On 8/6/07, Bobby Rullo <br at osafoundation.org> wrote:

> To solve this in a server-side way would involve making a new type of
> Atom request which, given the original Item, and a new Item:
>         a) Persist the original item, which would have a new UNTIL date
>         b) Persist the new Item
>         c) Add the new item to all collections the original one was in
>         d) Move all modifications of the original Item which are past the
> UNTIL date to the new Item

could we define some sort of "detach" hint in the event record?

the hint would tell the eim translator to make a copy of the original
item, apply the changes described in the record set to the copy,
calculate the new recurrence rule for the original item, add the copy
to all of the original's collections, and reparent the appropriate
modifications.

this would keep us from having to extend the protocol in a potentially
awkward way, would retain atomicity of the operation, and would
centralize the complex logic in the subsystem that handles the
majority of our model weirdness (the eim translation layer).

what specific information would the hint need to convey?