| Note: This tutorial assumes that you have completed the previous tutorials: Understanding Zeroconf. |
 Please ask about problems and questions regarding this tutorial on answers.ros.org. Don't forget to include in your question the link to this page, the versions of your OS & ROS, and also add appropriate tags. |
Understanding Service Types
Description: Explains the zeroconf service type formats.Keywords: zeroconf
Tutorial Level: BEGINNER
Syntax
_ServiceType._TransportProtocolName.
Note especially:
- Each part must start with an underscore, '_'.
- The second part only allows '_tcp' or _'udp'.
If you blaspheme and do not include the underscores you will...die a horrible death.
Actually, there is a reason lost in time for it. I just can't remember now, but will add it here when I rediscover it.
Common Examples
Zeroconf service types are identified by a string, e.g. some common ones include:
_scanner._tcp _http._tcp _webdave._tcp _tftp._udp
Semi-Official Ros Service Types
Although we're not keeping an official list anywhere (yet), the current ones that are common to test cases include:
- _ros-master._tcp, _ros-master._udp
- _concert-master._tcp, _concert-master._udp
- _app-manager._tcp, _app-manager._udp
We may include some utilities to help translate between these cryptic names and human readable names at some point in the future.
