> The bare minimum required for Chandler to share collections with other > Chandlers is a plain old WebDAV server. In this scenario, publishing > a collection to the server means Chandler MKCOL's a DAV collection and > then PUTs an XML file for each item in the collection; or optionally > Chandler can instead PUT/GET a monolithic .ics file representing a > collection. If you have a CalDAV server, Chandler should support that > too for the most part. By far the most tested path for sharing is the > Chandler <-Morsecode-> Cosmo way. >
Thanks for the info. The reason I am asking is I am developing a "cloud database" and I would like to be able to support different client tools. I dont want to do anything where the data is "dumb" like webdav, but caldav or something higher in the food chain would be cool. I like caldav because it seems to have a fair amount of support. If morse code is fairly easy to do I might consider that, but given where things are at right now I am thinking a safer first step would be caldav. I was intrigued by carddav because it feels like there is no good standard for contact information on a server. I know there is LDAP, which I dont know much about but it seems not really mainstream for regular users. It does seem weird that nothing else exists. Just trying to figure out if there is a way to support chandler without too much work basically. Hank _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
