[Chandler-dev] Re: [Cosmo-dev] Re: [Dev] Re: [Cosmo] Apple iCal &
morgen at osafoundation.org
Wed Mar 15 14:23:14 PST 2006
On Mar 15, 2006, at 2:06 PM, Mimi Yin wrote:
> Hi Heikki,
> I think the UI problem we face is how do we communicate to the user
> to do that?
> Chandler user sends an URL to an iCal user:
> A) How does the Chandler user know which URL to send. Can they send
> either read-only or read-write? Or do both work?
Both would work since iCal is a one-way calendar client -- it either
publishes *or* it subscribes, not both. It only works both ways when
syncing iCals on other computers via .mac.
> B) iCAL user receives URL, has never heard of Chandler. How will
> iCAL user know to remove the "s"?
> I think our over-arching goal is still to Get Users. We think
> interoperability is on the critical path to getting users. iCal is
> the only calendar client we interoperate with today.
> I don't have an opinion on turning off HTTPS. For some people,
> security will be more important than interoperating with iCal. For
> others it won't be. But I think we can come up with a solution that
> makes iCal interoperability discoverable without putting people's
> data at risk.
The only user-friendly solution I can think of is to add the hack I
described in my previous email. ("if we've just published a
collection to this specific host (cosmo-demo.osafoundation.org) over
port 443, then return three URLs, otherwise return two.")
More information about the chandler-dev