Vice-versa, and perhaps more importantly; any calendar created by iCal 3 through CalDAV will not be viewable by older, WebDAV-based clients. Hopefully, this little exercise has not been entirely confusing... :-) E 28 okt 2007 kl. 14.10 skrev Emil Lundberg:

Hi Douglas,

(DCS folks, feel free to correct me if I am mistaken)

DCS at its core is a WebDAV server (basically HTTP with r/w capabilities), allowing any user to upload files (not necessarily .ics/iCalendar files) to a any permitted directory using the proper credentials. This can also be accomplished using the DAV extension to a standard Apache httpd web service.

While it is entirely possible to allow iCal 2 (or Outlook 2007, Windows Vista Calendar, Evolution, etc) clients to publish and subscribe to calendars residing in the DCS collection space, CalDAV- aware clients (such as iCal 3, SunBird/Lightning or Mulberry) will never be able to access these directly through their CalDAV accounts. Rather they will have to subscribe/publish to them as they would any other web-calendar, and all the CalDAV-specific functionality (delegations, acl, free-busy, true server-based calendars, etc) will be lost.

Basically, you will have to decide what level of functionality you are aiming for; if all you need is to publish/subscribe to web calendars, you just require a WebDAV server (even Exchange has some support for this, IIRC). Taking the CalDAV route promises much more but has the downside of being a work in progress and also limits your current choice in clients. This is expected change rather rapidly however :-)

best,

/Emil

28 okt 2007 kl. 07.26 skrev Douglas O'Connor:

...

Hello again,

I have found that I can still publish to the DCS with the older 10.4 iCal (v2.0), which the online documentation says is not compatible, as long as it is done in the root directory and with the admin/admin uid/pwd. For example, publishing to http:// www.servername.edu:8008/ with admin/admin is no problem. It has a problem unpublishing, but the ability to publish and subscribe is there for older versions of iCal.

I am wondering if, since it is possible for this to happen on the root dir with the admin guid, can I somehow config DCS to let it happen across the server, in other dir structures? Is there a reason why I wouldn't want this? Normally when I try this, I get: Calendar data does not conform to CalDAV requirements: METHOD property is not allowed in CalDAV iCalendar data. But it seems important that servers be somewhat backwards compatible, so that not everybody has to go out and buy new software in order to take advantage. Additionally, why wouldn't I receive the same error message as an admin/admin publishing to the root dir?

Any ideas would be welcome, thank you all very much for helping out.

-Doug _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users

_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users

...

Vice-versa, and perhaps more importantly; any calendar created by iCal 3 through CalDAV will not be viewable by older, WebDAV-based clients.

Hopefully, this little exercise has not been entirely confusing... :-)

Actually that is not quite right. Our server will return an entire .ics file if you do a GET on the CalDAV calendar collection. e.g. if you point your WebDAV calendar client to /calendars/users/ cdaboo/calendar on the server (using your own user id and a valid calendar name) you should be able to "Subscribe" to the calendar. You won't be able to "publish" to that calendar, but if all you want is read-only access then that will work.

Note, however, that this is a "private" extension to CalDAV - there is no guarantee it will always work that way, though there isn't any obvious reason why it would change.

Several other CalDAV servers have implemented the same behavior as the ability to subscribe like this is handy to support existing web- calendar clients.

-- Cyrus Daboo

Neat, I wasn't aware of that. Coupled with the fact that it's possible to publish/subscribe to a calendar located at e.g. / calendars/users/cdaboo/old_calendar.ics, I guess this is about as much legacy support as one could ask for. /Emil

Yes, I can confirm that I got CalDAV working in Mulberry, the setup is just in a different place than you might expect (at least it was for me). To configure, go to File-->Preferences, and in the accounts tab, create a new account of type "CalDAV Calendar". Here, you can enter your info such as username, server name, and calendar path. Once that's set up, you can go to Mulberry's main calendar tab, and the account you just created should be listed, and expanding that will reveal your calendar server hierarchy. To modify permissions, simply right-click the object you want to edit, click Details, and go to the Access Control List tab. Hope that helps. Darren Ernesto Revilla wrote:

Hi.

I checked the FAQ of mulberry (http://www.mulberrymail.com/faq/index.shtml), but I didn't see anything about CalDAV compatibility.

Could Cyrus Daboo or anybody else put a comment about CalDAV compatibility in Mulberry? (I'm not subscribed to any Mulberry mailing list.)

(I read that Mulberry can manipulate WebDAV ACL lists.)

Best regards Erny

__________ NOD32 2622 (20071028) Information __________

This message was checked by NOD32 antivirus system. http://www.eset.com ------------------------------------------------------------------------

_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users

__________ NOD32 2622 (20071028) Information __________

This message was checked by NOD32 antivirus system. http://www.eset.com