/htdocs/caldav.phpCalDAV Server - main program
include_once
(caldav-OPTIONS.php)
(line 52)
include_once
(caldav-GET.php)
(line 61)
include_once
(caldav-REPORT.php)
(line 53)
include_once
(caldav-PROPFIND.php)
(line 54)
include_once
(caldav-MKCALENDAR.php)
(line 56)
include_once
(caldav-PROPPATCH.php)
(line 55)
include_once
(caldav-PUT.php)
(line 58)
include_once
(caldav-MKCALENDAR.php)
(line 57)
include_once
(caldav-LOCK.php)
(line 64)
include_once
(caldav-GET.php)
(line 60)
include_once
(caldav-DELETE.php)
(line 62)
include_once
(caldav-POST.php)
(line 59)
include_once
(caldav-LOCK.php)
(line 63)
include_once
(test-RRULE.php)
(line 66)
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 Sat, 12 Sep 2009 00:11:57 +1200 by phpDocumentor 1.3.2