[Dev] Re: [Cosmo] Free/Busy in Chandler 0.7
morgen at osafoundation.org
Tue Mar 7 18:04:27 PST 2006
Comments about B) and E) below...
On Mar 7, 2006, at 5:24 PM, Jeffrey Harris wrote:
> B) Chandler calculates free-busy based on what's in My Calendar and
> periodically updates a collection of VFREEBUSY components.
> VFREEBUSY components are more compact than full VEVENTs, so the
> upload-twice problem is diminished somewhat. It still suffers from
> non-Chandler propagation delays.
+1, and I think a slight delay is not a big deal.
> E) Apparently semantics will be added to CalDAV in the next month
> or so
> that setting a particular property on a calendar collection will
> events in that collection from being included in free/busy
> reports. Use
> those when they're implemented in Cosmo.
> In this scenario, Chandler just won't support Marilyn publishing
> managed for Lorenzo" in her own account without screwing up her
> free/busy until Cosmo adds these semantics, but that's not a crucial
> 0.7alpha2 use case, and there's a reasonable path between here and
> This scenario still suffers from free/busy not being perfectly up to
> date if "Sally's soccer practice" changes, but at least changes to
> "Work" and "Home" are reflected immediately in her free/busy.
> As you might guess, I think we should do E). This means creating a
> "Publish my Free/Busy information" menu item which creates an
> "events in
> My Calendar not otherwise published" collection (more reasonable name
> suggestions welcome) which gets published along with other
It's not clear to me how such a collection is computed. :-)
But since I am hearing that we will want Scooby to have access to our
calendars even if we haven't shared them with others (which I guess
makes sense), we're going to need to publish all our calendars to
Cosmo anyway, so therefore we won't have to compute the "EIMCNOP"
collection. If/when Cosmo implements the 'free/busy collection
property' feature you describe in E), then it seems like then you
would want a checkbox within Chandler for each collection indicating
whether or not the collection should be included in free/busy report,
and if that collection is not already shared to the Cosmo server on
which their free/busy info will live, the collection will get
published, and the free/busy collection property is set to
'include'. If the collection is already shared on that Cosmo server,
then the free/busy collection property is toggled appropriately.
One other thing to take into account is whether people will have
their calendars distributed on multiple servers. I know I will have
my work calendar on an OSAF cosmo instance but my personal calendar
will likely be on my own cosmo, which means I couldn't use option
E). Option B) would still work in that case though. Also, in option
B), does it need to be a collection, or would a monolithic ICS file do?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chandler-dev