[cosmo-dev] Re: iCal 3 interop - problem creating calendars

[Ted Leung]

Because of this we're going to try and get add/remove collection into  
0.9.

On Nov 6, 2007, at 1:13 PM, Brian Moseley wrote:

> On Nov 6, 2007 11:20 AM, Brian Moseley <bcm at osafoundation.org> wrote:
>> bug 11216 (<https://bugzilla.osafoundation.org/show_bug.cgi? 
>> id=11216>)
>> describes the problem that occurs when an iCal 3 user tries to create
>> a calendar on Cosmo.
>
> i did some more investigation here. turns out that if i go ahead and
> give all authenticated users the read-free-busy-privilege when
> creating the calendar, iCal doesn't send the ACL request to set that
> privilege. good deal.
>
> however, iCal follows up by sending a PROPFIND to / for the
> calendar-free-busy-set property, which is a scheduling property. it
> sends that request to / because it thinks that's where the user's
> scheduling inbox is. it thinks that because Cosmo doesn't provide a
> property on the user principal resource that tells iCal where the
> scheduling inbox is. that's because Cosmo doesn't implement
> scheduling. so Cosmo responds to that PROPFIND to / with a 501 and
> iCal freaks out in the same way it did originally.
>
> this all boils down to the fact that iCal assumes the server it's
> talking to implements scheduling and privilege setting. it doesn't
> bother to check whether or not the server actually advertises these
> features. iCal is totally broken, and there's not really anything we
> can do to fix it or work around it.
>
> i think we just have to tell our users that they can't use iCal to
> make calendars :/
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev