All Classes and Interfaces

Class
Description
Free/busy over the platform's own calendars, under the platform's own calendar ACL and the target user's own sharing choice.
Publishes a calendar as a private, read-only iCal link that any calendar application can subscribe to.
 
Subscribes a user to a calendar link — an iCal or webcal URL — and keeps its events in a read-only personal calendar, refreshed periodically (EXO-90278).
One remote account a user connected to their agenda, identified by the connector (remote provider) it belongs to.
 
 
 
 
 
 
 
 
 
 
 
Finds the clashes on a user's own calendar over a window.
 
 
One attendee's clash with a proposed window: who, and the span of the window they are busy over.
The clash report over a proposed window, for the attendees whose availability the asking user is allowed to read.
What actually happened when one user's busy time was asked for on behalf of another — the per-user status of a busy-time read.
Whether a user lets the platform disclose when they are busy — time ranges and nothing else.
 
 
The private, read-only link through which a calendar application subscribes to one eXo calendar (an iCal feed).
 
 
A user's subscription to a calendar link (EXO-90278): the remote iCal feed, the personal calendar its events are imported into, and the state of its refreshes.
One occurrence a subscription imported (EXO-90278): which agenda event holds it, its stable identity in the feed, and the digest of what was imported, so that a refresh updates the event rather than duplicating it, rewrites it only when it changed, and removes it when the feed no longer carries it.
 
 
 
 
 
 
 
 
 
 
 
 
A tokenised invitation link that is no longer answerable, because the meeting it answers is over.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Whether an event's content may be read outside eXo (EXO-90322).
 
 
Answers, for the add-on that writes meeting copies into a user's connected calendar account, whether it is going to write one — asked by agenda before it decides anything that depends on the answer.
 
 
One clash on a user's own calendar: a set of events that overlap in time, with the window they span.
One event of a ScheduleConflict, with the two things a caller needs in order to say something useful about it and that the Event alone does not carry: what the asking user answered to it, and whether it is theirs to move.
Every clash found on one user's calendar over one window, and whether the search saw the whole window.
A half-open time range [start,end[ used by the free/busy algebra.
One user's availability over a window: the time they are busy, and the time they are not.
One user's busy time over a window, and what happened when it was asked for.