#270: How should calendar discovery work? ------------------------------+--------------------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED] Type: Defect | Status: closed Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Resolution: Completed | Keywords: ------------------------------+--------------------------------------------- Changes (by [EMAIL PROTECTED]):
* status: new => closed * resolution: => Completed Comment: If you start at your calendar principal (eg, for me, /principals/users/wsanchez/), then there are DAV properties to help you find you calendar homes. Also, if you start at /principals/ on our server, you can look up your own calendar principal URI via the DAV:current-user-principal-uri (or something) property. The idea there being that if you do an CalDAV SRV DNS record lookup for example.com, that would resolve to something like https://calendar.example.com/principals/, where you can then to the current-user-principal lookup, and then the rest of the CalDAV lookups. Is that enough info? -- Ticket URL: <http://trac.calendarserver.org/ticket/270#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server _______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev