Package org.exoplatform.caldav.model

Class PendingPush

java.lang.Object
org.exoplatform.caldav.model.PendingPush
public class PendingPush extends Object
One write eXo owes to one calendar copy and has not managed to make.

Why this exists at all. A push that fails used to leave nothing behind. The log said the verification pass would retry, and the verification pass never could: its first gate compares the version the server publishes against the version eXo recorded, and an edit that never reached the server does not move the server's version. The copy was therefore judged untouched before anything was fetched or compared, and stayed wrong for ever. A failed removal was worse still — a destroyed event renders to nothing, and no pass concludes anything from an empty render.

So eXo records the obligation on its own side. Nothing here is a claim about the server: it is a claim about what this connector has and has not done, which is the only thing it can know without asking.

Flat, for the reason CalendarSync explains.

  • Constructor Details

    • PendingPush

      public PendingPush()