[Cosmo-dev] morse code and dav sharing mix

Morgen Sagen morgen at osafoundation.org
Mon Apr 30 11:34:26 PDT 2007

On Apr 30, 2007, at 11:08 AM, Grant Baillie wrote:

> On 30 Apr, 2007, at 10:27, Randy Letness wrote:
>> There was a bug submitted:
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=8946
>> that deals with using dav to subscribe to a collection published  
>> with morse code.  Should this even be supported?
> IMHO: no.

A CalDAV client should be able to subscribe to (and modify) a  
morsecode-published collection.

>> Will newer versions of Chandler support dav sharing?
> I believe need some version of Chandler to be able to read "old"- 
> style DAV archives, so that people can migrate their data to  
> morsecode. I don't remember whether obsoleting DAV completely from  
> the client is supposed to happen for Preview or not. And CalDAV  
> will still be supported, of course.

At some point soon we will remove the support for dual-fork ICS/XML  
sharing from Chandler (after TBD numbers of users has migrated to  
morsecode), but Chandler will always continue to be a CalDAV client  
as well as a morsecode client.

> Also, I'm not sure what the plan is, but determining which kind of  
> share we're dealing with is something a client can detect. So, it  
> seems to me to be a Chandler Desktop bug if there's a morsecode  
> share that we try to subscribe to as a DAV share.

Once we have removed support for dual-fork ICS/XML shares from  
Chandler, from that point on handing Chandler a CalDAV URL (i.e., a  
DAV collection of type "calendar") will cause Chandler to subscribe  
as a CalDAV client, as I don't think there is a way for the client to  
know that a given CalDAV collection *also* has a morsecode interface  
to it, and what the URL would be without some intelligent "guessing"  
on the client's part.  If we need different behavior, this needs to  
be spec'd out.

> --Grant
>> If so, then this might be confusing to the user because the only  
>> data that would be shared between users using dav and morse code  
>> is event data.  Anything else is stored as .xml in dav resources  
>> that morse code clients won't be able to sync against.
>> The same goes for subscribing to a collection originally published  
>> with dav.
>> -Randy


More information about the cosmo-dev mailing list