[Gpephone-devel] Calendar Scheduling

[zze-Ost SEBASTIEN A ext RD-ILAB-PEK]

Hi ,

 

I'm working on group scheduling functions in calendar enabler.

 

There're following questions up till now.

1- Our function should require an instance ID when working with iCals so
that just one instance can be canceled or rescheduled or ... for a
repeating event, in the way it is specified by the RFC (if no RID is
specified, the modifications are to be applied to the whole component) .

 

2- We could provide shortcut methods for the iTIP methods that are
simple (publish for example)

 

 

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?

 

 

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?

 

 

5- I'm going to draw the diagrams for the incoming and outgoing iCal
process.