Draft
Conversation
Change-Id: I61c77b2966a97b499ce975cc0725f1cc20ff0ab2
Author
|
It could perhaps be useful to let the object access function know whether the access is local or remote, so they can e.g. skip validation for local writes (such as for the PDO configuration objects). Object initialization from defaults and store should also be local then. |
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I needed to configure some PDOs dynamically based on application state. This was the only way I could do it, because the PDO configuration objects are otherwise only accessible via the bus. The same mechanism may be useful for other things.
It could also be useful to access large objects synchronized with the c-open thread, but for that the API functions should probably take void* and size instead. Something to consider.