separating ActionServer implementation into base class and ros-publisher-based class #11
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.
Currently, if one wants to implement an action server in an environment with the same datatypes but a different transport mechanism (like in orocos) then one has to re-implement the entire actionserver interface (see: oro_action_server )
This instead separates the ActionServer class into ActionServerBase and ActionServer, where ActionServerBase handles callback routing with the goal handles, and ActionServer handles the actual publishing of data over ROS topics.
@konradb3