Package org.exoplatform.caldav.client.bluemind


package org.exoplatform.caldav.client.bluemind
  • Class
    Description
    Reads the access control list of a BlueMind calendar through BlueMind's own REST API — the one place its sharing state can be read (EXO-90253).
    One entry of a BlueMind container's access list.
    Writes and removes calendar objects through BlueMind's own calendar REST API — the door whose every change carries sendNotification=false (EXO-90307).
    What one import task reported when it ended.
    How the poll loop waits between two status reads — a seam, so a test can drive the deadline without spending the time.
    Whose each calendar in a BlueMind account's view is, as BlueMind's own subscription listing reports it (EXO-90347).
    Whose calendar a BlueMind collection is, read from the container uid the server names it by (EXO-90275).
    A subscription the naming revealed: whose uid the container carries, and whether that uid is a resource's.
    The BlueMind door: every write is an ICS import, every removal a REST delete with notifications off, and the version eXo records afterwards is the one the collection's own listing publishes (EXO-90307).
    The one way eXo talks to BlueMind's own REST API: a session opened with the account's stored login and password, kept per account for a short while (see call), every call carrying the key it answered.
    An answer: status and body text.
    BlueMind as a server flavour: recognised by its registration's name, it may write through WriteChannel.BLUEMIND_IMPORT, and it keeps a REST session per account (EXO-90397) that eXo drops when the account or the registration changes.
    The BlueMind REST session each account currently holds, kept in this node's own memory for a few minutes so that a burst of reads costs one login rather than one login per read (EXO-90397).
    The account a session belongs to.
    Sharing a BlueMind calendar with a colleague (EXO-90253, EXO-90277, EXO-90378): Apple's POST CS:share over DAV, every change confirmed by reading the container's access list back through BlueMind's REST API (BlueMindAclClient), and the colleague subscribed to the calendar once a grant is confirmed.
    The session BlueMind opened belongs to somebody other than the account eXo meant to edit, so nothing was sent (EXO-90277).
    BlueMind's subscriptions as a channel: its container naming (BlueMindContainerNaming) tells a subscription from the account's own calendar, and its REST subscription API (BlueMindSubscriptionClient) subscribes a colleague to a calendar shared with them (EXO-90275, EXO-90277, EXO-90347).
    Edits a colleague's own BlueMind subscriptions through BlueMind's REST API, as that colleague (EXO-90277).
    The edits one open session, checked to be the colleague's own, can make.
    Contributes BlueMind's import door for WriteChannel.BLUEMIND_IMPORT.