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
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/calendarserver-users
