connected is a boolean, but getBusStats is underdeveloped and unused
right now, so I wouldn't worry about it (or use it). The API was meant
for a tool that hasn't had high enough priority yet.

For requestTopic, the assumption is that the subscriber would send a
machine ID along with the request for shared memory. The subscriber
sends a list of lists, where each list is a transport name plus any
additional parameters necessary for validating that transport, like IP
address.

The general protocol is the subscriber sends an ordered list of
protocols, and the publisher selects a valid one. The subscriber
should still send other fallback protocols in the shared memory
protocol is not achievable.

hope this helps,
 - Ken


On Wed, Jul 7, 2010 at 6:19 AM, Andrew Harris <andrew.unit@gmail.com> wrote:
> Hello,
>
>   I'm looking at the slave API here:
>
> http://www.ros.org/wiki/ROS/Slave_API
>
>  I have a couple easy questions.  First, in pubConnectionData there
> is a "connected" field.  I am curious about what type that field is,
> in terms of XMLRPC types.  Second, in requestTopic, if there were a
> shared memory protocol, what is the recommended way to figure out
> whether this potential subscriber is on the local machine? Would it be
> to make a lookupNode() RPC call to the master and comparing the IP
> addresses?
>
> thanks,
> -andrew
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>