[Cosmo-dev] This and Future issues

[Randy Letness]

Brian Moseley wrote:
> On 8/8/07, Randy Letness <randy at osafoundation.org> wrote:
>
>   
>> 2. Include's a couple parameters in the request like "thisAndFutureUuid"
>> and "thisAndFutureLastOccurrence" that contains the uuid of the master
>> item that this new series is "breaking" and the last occurrence of the
>> series.
>>     
>
> if by request parameter you mean eim field, sure
>   

No I was thinking request parameters like in the URL so that the 
protocol layer has access to them (like in the time-range queries).  I 
don't think we can handle this in the eim translation layer because that 
layer is designed to operate on a single item.  The layer above it is 
responsible for actually making the service call to create/delete/update 
the item.  Since we need a single service call to potentially 
create/update/delete multiple items I think we have to handle this 
similar to the way we handle startDate changes on recurring items.  So 
we would have a similar processEntryCreation() method in ItemProvider.

Thinking about it more, we only need a single parameter, which is the 
uuid of the occurence or modification that the user is editing.  That 
gives us the parentUuid and the last recurrenceId.

-Randy