[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] icaldir Proposal
From:       Mark Bucciarelli <mark () easymailings ! com>
Date:       2006-02-09 22:35:37
Message-ID: 20060209223537.GP3480 () rabbit
[Download RAW message or body]

On Thu, Feb 09, 2006 at 10:11:44PM +0000, David Jarvie wrote:
> On Thursday 9 February 2006 19:12, Mark Bucciarelli wrote:
> >I agree with your point--everyone using the icaldir _must_ work with a
> >common set of VTIMEZONE data or all hell will break lose.
> >
> >One way to ensure this is to use a timezone registry file (as the ical
> >RFC allows), and put this registry file in the icaldir. Then have the
> >spec limit TZID's to reference this registry.
> >
> >This answer's David J's concerns as well--if an app needs a new
> >VTIMEZONE object, they must add it to the registry.
> >
> >So the time zone registry is a subdirectory, with one file for each
> >VTIMEZONE object.
> >
> >Hey, what do you know? That's what /usr/share/zoneinfo looks like. That
> >seems like a good sign ... ;)
> 
> But what if the received VTIMEZONE object has the same TZID as an existing 
> registry entry, but differs in its definition?

You mean someone emails you a meeting request that includes a TZID that
matches one in your registry, but has a different definition?

First, to be able to do anything, the meeting request must
include the VTIMEZONE definition for that TZID.

Then, the icaldir lib should check this VTIMEZONE def against the
registry, recognize the conflict, look for another TZID in the registry
with the same def, use that if found and if not found, generate a
new unique TZID, register it, then write the event. Cumbersome, but
consistent.

m

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]