[Cosmo-dev] recurrence modifications and multiple collections

[Randy Letness]

Jeffrey Harris wrote:
> On Cosmo, what happens if I delete a modification from a recurring
> series?  Does the modification go away for all collections the master
> appears in?
>   

Actually cosmo will only remove that modification from the collection, 
which means if that modification exists in more than one collection you 
have to remove it from all collections in order to fully remove the 
modification.  Does Chandler support modifications that exist in one 
collection, but not another? 


> If so, when we remove a master event from a collection, we don't want to
> be deleting modification records unless the master isn't in any other
> collections.
>   

Right, this is how cosmo works now.  When a master event is removed and 
doesn't exist in any other collections, the event and all its 
modifications are deleted from the server.


> Right now I believe that Chandler is sending modification-record
> deletions when a master event is removed from a collection.  I'm now
> thinking this isn't right, I think since Cosmo is potentially managing
> the recurring series in multiple collections, Cosmo needs to manage
> modification records without Chandler's involvement.  Does that seem right?
>
>   
Actually I think this is right.  If a master event with modifications 
exists in two collections, then in order to remove the event with 
modifications from one collection, a delete for the master and a delete 
for each modification has to be sent.  This tells cosmo to remove the 
master and modifications from the collection. Otherwise you end up with 
the modifications in two collections and the master in one, which 
doesn't really make sense.  Maybe cosmo should automatically remove all 
modifications when a master is removed from a collection to prevent 
this.  And it should also interpret a remove modification as "remove 
from all collections" because cosmo can't handle modifications that 
exist in one collection, but not another.

-Randy