## page was renamed from zeroconf_implementations/Tutorials/Understanding Zeroconf Service Types ## For instruction on writing tutorials ## http://www.ros.org/wiki/WritingTutorials #################################### ##FILL ME IN #################################### ## for a custom note with links: ## note = ## for the canned note of "This tutorial assumes that you have completed the previous tutorials:" just add the links ## note.0= [[zeroconf/Tutorials/Understanding Zeroconf|Understanding Zeroconf]] ## descriptive title for the tutorial ## title = Understanding Service Types ## multi-line description to be displayed in search ## description = Explains the zeroconf service type formats. ## the next tutorial description (optional) ## next = ## links to next tutorial (optional) ## next.0.link= ## next.1.link= ## what level user is this tutorial for ## level= BeginnerCategory ## keywords = zeroconf #################################### <<IncludeCSTemplate(TutorialCSHeaderTemplate)>> == 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. ## AUTOGENERATED DO NOT DELETE ## TutorialCategory ## FILL IN THE STACK TUTORIAL CATEGORY HERE