What are/are there caveats in using multiple transport::node objects in a single process?

asked 2017-12-18 20:54:37 -0500

asomerville gravatar image

In our code base I've seen a pattern of passing around a single node object and making all the calls to advertise and subscribe with that node object. It would seem to be easier to allow different classes to make and maintain their own instances of a gazebo::transport::node, but I can't seem to find any documentation which specifically talks about whether this is a particularly bad idea.

Is this a supported mode of use?

Are there things to watch out for when doing this?

edit retag flag offensive close merge delete