Toltec connector and exceptions to recurring events

[Alan J Collison]

I was hoping someone could clarify the following observed behavior:

Using Outlook with the Toltec connector and connecting to Kolab,
I created a recurring event.  I then changed the location for
one instance of the recurring event, leaving all the others the
same.  Since the Kolab data format does not support RECURRENCE-ID
(or some equivalent), I was expecting that perhaps the single
series of recurring events would be broken up into 2 parts:
the original series without the one exception and a new single 
event corresponding the the instance with the new location.
I see no other way to handle this with the Kolab data format.

However, what happened was that an exception was added for that
one instance and no new event was created.  Looking at the
data, it's apparent that Toltec is storing a RECURRENCE-ID (or equivalent) and
information about the exception to the recurring series of events.
So, in Outlook, everything looks o.k.  However, if I use another
client which relies on the Kolab data, it would see something 
different I think: it would see a recurring series of events with
a hole in the series on the date of the specified exception.
In other words, the event ocurring on the day of the exception has
effectively disappeared, even though that exception is not a cancellation
of the event instance.

So, what I am wondering is which of the following is true:

1. This is considered a problem/limitation in the kolab
   data format

2. This is considered a problem in the behavior of the Toltec
   connector

3. This is not considered a problem (and if so, why?) :)

Alan


_________________________________________________________
XO Hosting and Email: Great Service, Great Features, Great Support!
http://register.cnchost.com/offers/referral/referrer=collison.net/