Cache Event Subscription
Description
[IDM.TSA.E1.00017]
If a data update event occurs from the distributable cache, the task controller MUST execute a policy which evaluates whether any further tasks must be created. If any task is configured, the tasks MUST be created for execution. The task has the same metadata as the event. (key, namespace and scope)
For instance: A proof data object is inserted from the OCM into the cache. This object contains a DID from the issuer. The policy evaluates the schema of the data object and returns Task “IssuerProof”. The task controller inserts this task to the tasklist by adding the http URL of the OCM proof manager with the DID of the issuer as parameter. Some seconds later, the proof from the issuer arrives and the policy returns null (nothing to do).
* Constraints
Distributable Cache Event
Policy Evaluation
* Input
An Insert/Update Event
* Output
A task result or null.
Acceptance criteria
- After an update event in the distributable cache, a task must be created as pre-configured (or dynamically by policy).