When several instances of KuneAgi run in parallel, each dealing with its own category of Action Proposals, they need to share a single Cooperative Behaviour Mark (CBM) for each user, as described in Issue #51.
As described in that same Issue #51 and in the corresponding Issue 135 of KuneAgi, the fields "Cooperative Behaviour Mark" and "Latest Update of Cooperative Behaviour Mark" of a user are updated in the LDAP directory each time one of the KuneAgi instances experiences an allocation of a new input for that user.
As soon as AlirPunkto has received an update from one instance of KuneAgi, it should update all the other instances of KuneAgi with the new values of:
Cooperative Behaviour Mark
Latest Update of Cooperative Behaviour Mark
Thereby, all these instances can carry on computing the correct value of the Cooperative Behaviour Mark of the user, in real time, locally.
When several instances of KuneAgi run in parallel, each dealing with its own category of Action Proposals, they need to share a single Cooperative Behaviour Mark (CBM) for each user, as described in Issue #51.
As described in that same Issue #51 and in the corresponding Issue 135 of KuneAgi, the fields "Cooperative Behaviour Mark" and "Latest Update of Cooperative Behaviour Mark" of a user are updated in the LDAP directory each time one of the KuneAgi instances experiences an allocation of a new input for that user.
As soon as AlirPunkto has received an update from one instance of KuneAgi, it should update all the other instances of KuneAgi with the new values of:
Thereby, all these instances can carry on computing the correct value of the Cooperative Behaviour Mark of the user, in real time, locally.