Uses of Package
org.exoplatform.caldav.client

Package
Description
 
  • Class
    Description
    The CalDAV protocol, and nothing else: it fetches, it does not decide.
    Where a CalDAV conversation is allowed to go: the scheme and authority of one administrator-declared server, plus the account's base collection path on it.
    The one failure the CalDAV client throws for protocol and transport trouble: the server unreachable, an answer outside the accepted statuses of the verb, a body that is not DAV XML, or a target this client refuses to address.
    One calendar collection as a PROPFIND listed it: everything the sync engine binds a pair on, and nothing it does not need.
    One calendar object (an .ics resource) as the server answered it.
    What an MKCALENDAR answered — deliberately never a boolean "created".
    What a conditional PUT answered.
    Which incremental-sync tier a collection's server can serve, read from one Depth:0 PROPFIND (supported-report-set, ctag, sync token) plus the DAV response header.
    The incremental strategies of the plan, cheapest first.
    What an RFC 6578 sync-collection REPORT answered: the hrefs that changed, the hrefs that are gone, and the token to store for the next run.