[Documentation] [TitleIndex] [WordIndex

Stack Proposal Review

General Details

Date: 12th October in irc [irc.oftc.net,#ros][4pm EST, 2pm San Frans time]

Proposer: Daniel Stonier

Present at the Review:

Interested Parties:

This review is to establish the direction and API for the zeroconf_implementations stack via common consensus from interested parties in the ros community.

The zeroconf_avahi and zeroconf_avahi_demos present a fairly complete, working example of the avahi implementation on linux. This is the currently planned direction for the zeroconf implementations.

Question / concerns / comments

Enter your thoughts on the API and any questions / concerns you have here. Please sign your name. Anything you want to address in the API review should be marked down here before the start of the meeting.

Topics:

Actions:

kwc

My high-level comment is that we need to establish use cases as there are chicken-and-egg problems in some of those cases. The current zeroconf stack layers on top of a running ROS system and uses ROS, which means that ROS itself cannot use zeroconf -- but this approach means you get some nice ROS APIs to manipulate zeroconf in a generic way.

I actually took care to separate it into two components to handle such use cases. zeroconf_avahi is currently a c++ library and a ros node. The c++ lib has scattered ROS_xxx's scattered around since I was debugging, but they'll come out, leaving it as a pure c++ library. If ros itself decides it wants to do zeroconf internally, its just a matter of moving the library itself to wherever it needs to be. [Daniel Stonier]

Meeting agenda

Conclusion

Immediate:

Later:

The last one needs some testing to see just how avahi behaves. It is also perhaps a bit non-trivial as to when and how we should remove a ghost service.



2023-10-28 13:11