Client behaviour improvements #135
Conversation
docs/Behaviour - Client Side.md
Outdated
|
|
||
| If keeping the configuration of the Sender, the Controller MUST `GET /constraints/active` from the Sender and evaluate these Active Constraints against the Constraint Sets it has built. | ||
| If keeping the configuration of the Sender, the Controller MUST `GET /constraints/active` from the Sender and provide the User with the Active Constraints and the Constraint Sets it has built or with the results of evaluation the former against the latter if the Controller is able to do such evaluation. |
There was a problem hiding this comment.
This language will prevent a Controller to perform autonomous work as it MUST always provide to the User ... This is bad.
There was a problem hiding this comment.
I still prefer to keep the original text and changing the MUST for a SHOULD if the objective is to minimize the requirements of the Controller.
"If keeping the configuration of the Sender, the Controller SHOULD GET /constraints/active from the Sender and evaluate these Active Constraints against the Constraint Sets it has built. If the current Active Constraints allow streams, that would not be compliant with the Constraint Sets it has built, the Controller SHOULD inform the User that compatibility of the Sender’s stream with the chosen Receivers cannot be assured without replacing the Active Constraints."
No description provided.