-
Notifications
You must be signed in to change notification settings - Fork 372
Resource Manager extension to support management of reference interfaces from chained controllers. #664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resource Manager extension to support management of reference interfaces from chained controllers. #664
Conversation
d38a8ff to
7f00914
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good. I think it was a good idea to make it part of ResourceManager.
7f00914 to
9a58545
Compare
9a58545 to
2dbd938
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me!
2dbd938 to
767c247
Compare
| resource_storage_->controllers_reference_interfaces_map_.at(controller_name); | ||
| resource_storage_->controllers_reference_interfaces_map_.erase(controller_name); | ||
|
|
||
| std::lock_guard<std::recursive_mutex> guard(resource_interfaces_lock_); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in other cases you put the guards into the function that is called. Is this different for any reason?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see above
This PR introduces changes for Resource Manager regarding management of reference interfaces from chained controllers.
Resource Manager already has implemented management of Command (Read/Write) interfaces, therefore only methods for accessing reference interfaces specifically are created.
The main reason for putting the code here is to avoid code duplication in Controller Manager.
The PR doesn't depend on any PR specifically because the changes and functionality is limited to Resource Manager.