Just an issue to keep track of thinking about this topic: should the "node" concept be interfaced via pyros directly ?
Currently the "node" is the endpoint of publishers, subscribers, and services (expressed in different ways : node name, uri, hostname:port, etc.)
Having a node concept would centralize this information
But that might start a tendency to focus on "node by node", "connection by connection" interaction, and it is especially what we want to avoid when manipulating distributed systems...
Note that it hasn't been necessary so far in my ROS interfacing usecase, so I m just wondering if there are usecases in which it would be useful ??
Just an issue to keep track of thinking about this topic: should the "node" concept be interfaced via pyros directly ?
Currently the "node" is the endpoint of publishers, subscribers, and services (expressed in different ways : node name, uri, hostname:port, etc.)
Having a node concept would centralize this information
But that might start a tendency to focus on "node by node", "connection by connection" interaction, and it is especially what we want to avoid when manipulating distributed systems...
Note that it hasn't been necessary so far in my ROS interfacing usecase, so I m just wondering if there are usecases in which it would be useful ??