The definition of 'calendar-home-set' is that it returns the URL of the
collection which contains the user's calendars. Not the URLs of the calendars
themselves.
then do a Depth: 1 PROPFIND on that
URL to retrieve the actual calendars
you will request the
resourcetype & supported-calendar-component-set
know which ones are calendars
whether they
support VEVENT/VTASK/VJOURNAL
public calendars
calendars for a
given user offered by other users
the dust isn't fully settled on
parts of this
a few tricks
Trick #1
PROPFIND request for current-user-principal
Also planned
query a 'well known URL'
find the right port
PROPFIND the /.well-known/caldav/ URL
Once you've *got* the principal-URL
PROPFIND for the group-membership
possibly do this repeatedly
Once *that's* fully
expanded to a list of principal-URLs
query the calendar-home-set for them
Depth:
1 PROPFIND on those to find their calendars
possible simplification
combine two steps
expand-property report is defined in RFC 3253 (WebDAV Versioning)
DAV::expand-property REPORT
can't think of a way to get the actual collections
maybe there is some trick
I guess at this point
current-user-principal in the first instance
PROPFIND Depth: 1 on the calendar-home-set
gets you the user's direct
calendars
differentiating
my approach would be
on demand
e.g. 'display delegated calendar'
principal-URL for the currently authenticated user
recursively PROPFIND
expand their group-membership into a tree
In DAViCal the public.php is specifically for looking at calendars which have
been declared to need no authentication