[Cosmo-dev] Re: [commits-cosmo] (rletness) [4318] Serialize datetime as floating instead of throwing timezone exception for

Brian Moseley bcm at osafoundation.org
Thu May 3 14:53:12 PDT 2007


On 5/3/07, svncheckin at osafoundation.org <svncheckin at osafoundation.org> wrote:
>
>
>  Revision 4318 Author rletness Date 2007-05-03 14:49:36 -0700 (Thu, 03 May
> 2007)
> Log Message
> Serialize datetime as floating instead of throwing timezone exception for
> unknown timezones.
>
> The use case is when a collection is updated by a CalDAV client that sends
> an unknown timezone. When Chandler syncs, it should receive a floating event
> if the the timezone is not supported.

i'm not sure that we should accept the caldav update if it sends a
timezone we don't understand.

you could make the argument that we should register and store the new
timezone, but that would require a database-backed timezone registry,
which we of course don't have at the moment.

is it better to throw away the unknown timezone from the caldav update
or to disallow the update altogether?


More information about the cosmo-dev mailing list