[Gpephone-devel] Calendar Scheduling

[lin]

Pls see following comments.

On Wed, 2007-03-21 at 02:54 +0100, zze-Ost SEBASTIEN A ext RD-ILAB
wrote:
>  Hi ,
> 
> 3- The sequence number is used to detect if the version of an iCal that
> has been received is older than the one currently in storage or not. A
> certain number of rules are defined in RFC2446 but it seems that
> Evolution or Outlook don't follow those rules. We should choose wether
> the application or the enablers are responsible for incrementing the
> sequence number.
> If it's the enabler, what policy do we use to increment this number.
> If it's the application, what interface do we provide?
> 
> What happens in the case of multiple events? Do they share the same
> sequence number or not?
When a "request" schedule reaches, the sequence number is the only clue 
to decide whether to update current local component. Therefore, I
 propose to increment the sequence each time the component is updated.
The enabler can do this automatically. 
As to multiple components(maybe main component and detached component)
 of the same event, the sequence number should be the same. 
Are there any other opinion?
> 
> 4- Based on the sequence number comes the question of when should we
> check that the received calendar is not outdated, when should we ask the
> user agreement to store a received iCal, should we keep the trace of
> canceled events (if a canceled event is just erased,then if we receive
> an older version of it, we're going to reschedule it but we shouldn't)?
> How long? Should they still be returned when calling a get_components or
> should they be hidden?
Oh , that's quite a complex situation But can you give a detail use case
in which, an older version schedule will be received after the event has
been canceled?
> 
> 5- I'm going to draw the diagrams for the incoming and outgoing iCal
> process.
Good! Expecting! :)


Lin