[chandler-users] Re: iCal 2.x usage of Chandler Hub

[Jared Rhine]

Jared Rhine wrote:
> This is a quick write-up of the use-case of 2 people using osaf.us to 
> coordinate iCal 2.x calendars.

The procedure I described earlier doesn't work.  In particular, issuing 
a ticket on a specific resource (your iCal 2.x *.ics file) doesn't work 
well.  Because iCal 2.x deletes your ICS before updating it.  When it 
deletes your ICS, your ticket for that file goes away as well.

So instead, to use iCal 2.x with osaf.us (in a "writable mode"), you 
should instead create a ticket on your *collection* that holds your ICS 
file.  Then you can use your collection ticket on your specific *.ics 
file inside iCal.  Currently, this URL will need to be formed manually 
(by appending "?ticket=whatever" to your *.ics URL).

iCal 3.x won't have this problem, at it will use CalDAV directly and not 
the (apparently broken) webcal delete/upload procedure.

This isn't a core use case for the Chandler products, but since I wrote 
up a procedure for chandler-users, I thought I should issue a correction 
to the same list for archival purposes.  Thanks.

-- Jared