Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Integrity communication covers conversations to collect information about state from the pillars, and conversations to re-establish a consistent state. Furthermore, the integrity will have communication to raise alarms and store logs and audit trails.


This illustrations depicts the conversations that may happen as part of the integrity client. It depicts conversations to retrieve state from pillars: get, getFilelist and getChecksums; conversations to restore consistent state: put and replace; and the conversations to store log information and raise alarms.

Note that neither of these communications are driven by the integrity client, but are rather operations in themselves. Thus, the integrity communications add no new elements to the protocol.

  • No labels