Timezone / recurrence scheduling discussion for Kolab

Georg C. F. Greve greve at kolabsys.com
Wed Nov 3 17:08:54 CET 2010

On Wednesday 03 November 2010 13.21:23 David Jarvie wrote:
> I'm not familiar with how Kolab stores its data, so I don't know what
> restrictions there are. From my experience, the only way to make this work
> reliably is to store the recurrence time as a local time with associated
> time zone (which is how the meeting time is actually specified by the
> person organising it), as in iCalendar. Then each client can convert the
> time to its own time zone, without any risk of error.

That is one of the proposed solutions, yes.

The only issue I currently see with it would be that we'd likely break 
backward compatibility, so there is a chance of confusion/data corruption 
between clients supporting format <=2.0, which assume storage in UTC, and 
those supporting 2.1 and greater, which would then store local time, both 
using the same tag for storage.

Does anyone have a good idea how to avoid this in a non-ugly way?

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20101103/c6fb335e/attachment.sig>

More information about the format mailing list