Feature #340

Implement Distributed Namingservice

Added by S. Wrede about 10 years ago. Updated over 5 years ago.

Status:FeedbackStart date:05/30/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:IntrospectionEstimated time:120.00 hours
Target version:rsb-1.0

Description

For introspection in an RSB system comprised by multiple transports, a nameservice implementation is needed.

In contrast to ROS, YARP, XCF, a distributed nameservice is required.

Implementation could be based on:

  • UPNP (btw: could enable DLNA-based use cases...)
  • Multicast-DNS (check compatibity)
  • ROS Master (at least evaluate it?)

Check relation to model-layer.


Related issues

Related to Robotics Service Bus - Feature #228: Introspection / Nameservice Interface and Initial Tool Su... Closed 03/18/2011
Related to Robotics Service Bus - Feature #44: Implement basic introspection support Resolved 03/24/2014 03/24/2014

History

#1 Updated by J. Moringen over 7 years ago

  • Category set to Introspection

#2 Updated by J. Moringen over 6 years ago

  • Related to Feature #44: Implement basic introspection support added

#3 Updated by J. Moringen over 6 years ago

  • Status changed from New to Feedback

For introspection in an RSB system comprised by multiple transports, a nameservice implementation is needed.

Given the above original motivation, I would like to reject this since #44 implements most of the practical aspects.

However, it may make sense to create a separate issue for discoverability of RSB transport, i.e. before a bus connection and thus introspection are available.

What do you think?

#4 Updated by J. Wienke over 5 years ago

Can we mark this as resolved or reject it. I think we have solved most aspects.

Also available in: Atom PDF