/htdocs/caldav.phpCalDAV Server - main program
include_once
(caldav-OPTIONS.php)
(line 37)
include_once
(caldav-GET.php)
(line 46)
include_once
(caldav-REPORT.php)
(line 38)
include_once
(caldav-PROPFIND.php)
(line 39)
include_once
(caldav-MKCALENDAR.php)
(line 41)
include_once
(caldav-PROPPATCH.php)
(line 40)
include_once
(caldav-PUT.php)
(line 43)
include_once
(caldav-MKCALENDAR.php)
(line 42)
include_once
(caldav-LOCK.php)
(line 49)
include_once
(caldav-GET.php)
(line 45)
include_once
(caldav-DELETE.php)
(line 47)
include_once
(caldav-POST.php)
(line 44)
include_once
(caldav-LOCK.php)
(line 48)
include_once
(test-RRULE.php)
(line 51)
require_once
("../inc/always.php")
(line 11)
CalDAV Server - main program
require_once
(HTTPAuthSession.php)
(line 14)
require_once
(CalDAVRequest.php)
(line 33)
From reading the "Scheduling Extensions to CalDAV" draft I don't think that we will be doing 'calendar-schedule' any time soon. The current spec is at: http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-03.txt
access-control is rfc3744, so we will say we do it, but I doubt if we do it in all (or even much of) it's glory really.
Documentation generated on Fri, 10 Apr 2009 23:45:51 +1200 by phpDocumentor 1.3.2