ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
If the service client is non-persistent (the default), the node implementing the server can change (eg. creash, respawn), and clients will properly reconnect when the next request is made. If the client is non-persistent, then you need to negotiate reconnections yourself.
More info for roscpp and rospy, respectively, can be found here:
http://wiki.ros.org/roscpp/Overview/Services#Persistent_Connections
http://wiki.ros.org/rospy/Overview/Services#Persistent_connections
2 | No.2 Revision |
If the service client is non-persistent (the default), the node implementing the server can change (eg. creash, respawn), and clients will properly reconnect when the next request is made. If the client is non-persistent, persistent, then you need to negotiate reconnections yourself.
More info for roscpp and rospy, respectively, can be found here:
http://wiki.ros.org/roscpp/Overview/Services#Persistent_Connections
http://wiki.ros.org/rospy/Overview/Services#Persistent_connections