Timing
- A check or usage report that gets no answer within 5 seconds counts as no answer.
- After a failed check, the package tries again after about 30 seconds, then about every 5 minutes, until a check succeeds.
- A process makes one check to start, and one more within 30 seconds of each new Session, to confirm its usage report. A save, a reopen that joins its Session, and the process exit send no check of their own unless usage counts are still unsent.
- In a browser page, the editor, the viewer and the layout engine check on their own. The editor starts a new layout engine for each document it opens, and that engine makes its own checks. A reopen that joins its Session is not billed again.
Queued usage reports
A new Session’s report must reach Reducto within 30 seconds of the first check that Reducto answers. The package sends it at once and, if the send fails, retries sooner than its usual backoff. Until a check confirms it, each call throwsundelivered, and the package retries every 30 seconds.
In a browser, engine.wasm also throws undelivered once 200 new Sessions wait for confirmation. It runs again when a check confirms them.
License check
POST /-/license:
counters are usage counts since the last check: document.open, document.parse, editor.open, viewer.open, editor.command.<name> and telemetry.dropped.
Usage reports
POST /-/events, in batches of up to 100 events, a few seconds after activity:
seq, chain, nonce and certificate let Reducto find lost and repeated reports. They are random or signed values and contain no data about you.