-
 

zeroconf_jmdns_suite package from zeroconf_jmdns_suite repo

zeroconf_jmdns_suite

Package Summary

Tags No category tags.
Version 0.2.1
License Apache 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/rosjava/zeroconf_jmdns_suite.git
VCS Type git
VCS Version indigo
Last Updated 2016-12-19
Dev Status MAINTAINED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

An implementation of zeroconf in pure java.

Additional Links

Maintainers

  • Daniel Stonier

Authors

  • Daniel Stonier

Zeroconf JmDNS

This repository packages android friendly sources from the jmdns project and provides some tutorial demos.

The JmDNS Library

About

JmDNS works a little differently from avahi, although it does the same job. You can separate its functionality into two parts:

1) Zeroconf services (publishing, discovery and resolution) on a fixed, specified interface. 2) Network topology aware zeroconf services (in the author’s language - multi-homed).

What the latter means, is that it will be automatically detect what network interfaces you have and also be aware of those interfaces going up and down whilst providing a dynamic awareness of the zeroconf services that appear and disappear with those interfaces.

The network topology part of jmdns is still fairly experimental.

The Experimental Part

The network topology aware part of zeroconf is quite important. On android in particular it saves you having to worry about detecting the ip of your interface, which is rather handy. This part is quite reliable after having helped with some patches upstream.

It does have problems however handling multiple network interfaces and can also be confusing with the way it handles ipv6. I have some patches here in this code set which get it working, but either aren’t upstream yet, or probably not the proper solution yet.

Hence we have a snapshot of the sources here.

Publishing

Publishing is relatively straightforward. For ros environments, we typically only ever want or need to publish the ros master, in which case you’d publish it under something like:

_ros-master._tcp 11311

Discovery

There are two methods in the jmdns library for discovery. The first is via polling, which will always be the far more reliable method (especially if your interface is up and down alot and likely to get jmdns confused). The second is via event based listeners which give you callbacks to instantly react on a zeroconf service coming up or down.

The Ros Wrapper

I’ve got a couple of classes set up to more easily handle the jmdns library for our purposes (jmdns can be quite messy to program with). It’s not a full node, but it wouldn’t be a stretch to convert this into a full node’s functionality using zeroconf_msgs as the basis for handles that work in a similar way to the ros zeroconf_avahi package.

Tutorials

Instructions can be found in the readme in the jmdns_tutorials package.

CHANGELOG

Changelog

0.2.1 (2015-02-25)

  • gradle 1.8 -> 2.2.1
  • Contributors: Daniel Stonier

0.2.0 (2015-02-18)

  • First build on indigo

0.1.13 (2013-11-01)

  • constrain open ranged dependencies.

0.1.12 (2013-10-31)

  • use ROS_MAVEN_REPOSITORY

0.1.11 (2013-10-25)

  • official maven style open ended dependencies.

0.1.10 (2013-09-23)

  • use updated ros gradle plugins with maven-publish for publishing.

0.1.9 (2013-09-22)

  • removing osgi information.

0.1.8 (2013-09-17)

  • bugfix install rule target name.
  • depend on rosjava_bootstrap for gradle plugins.
  • gradle wrapper 1.7
  • use catkin package xml version information
  • gradled, maven'd, deb'd.
  • ros-java -> rosjava migration.
  • refactoring for unique java package names.
  • fix badly copied package name for jdmns tutorial.
  • catkinization using rosjava_tools
  • demos working with new gradle build.
  • cleared out non jmdns packages.

0.1.7 (2013-04-29)

  • point at legacy rosinstallers.
  • using multiproject gradle now so we can add more projects here.
  • rosinstall file for rosjava.
  • bugfix for name in package.
  • readme added.
  • now building and installing with catkin.
  • first commit pulled in from kazuto's hg clone.
  • avahi and comms moved out.

0.1.6 (2012-07-17)

  • bugfix version bump.
  • refactored for ros code style format.
  • bugfix bad array size check, closes #35.
  • rosinstaller, use https, not git.
  • updated fuerte rosinstaller.
  • zeroconf: updated the rosinstaller for fuerte.

0.1.5 (2012-05-24)

  • updated rosdeps for rosdep2.

0.1.4 (2012-04-12)

  • Adjusting cmakelists for release into fuerte.
  • hoping to avert compilation of jmdns. Probably should divert to a separate stack.
  • new rosdeps.

0.1.3 (2012-01-04)

  • jmdns : better getInstance call.
  • jmdns: hack new jmmdns getInstance to always create, hack to trigger serviceRemoved callbacks on network down.
  • jmdns_demos : forgot to add the publisher class.
  • zeroconf_jmdns : added display names to the network interface logging.
  • jmdns : put default listener before the listener instantiation (sometimes add services will come in before it gets set otherwise).
  • zeroconf_jmdns : default listener to default discovery callback.
  • zeroconf_jmdns : now hiding all service_info api.
  • zeroconf_implementations : fix mediawiki formatting.
  • zeroconf_avahi : fix code after update to zeroconf_comms ip4/ipv6 upgrade.
  • zeroconf_jmdns: ros api utility toString function.
  • zeroconf: split the ros api to include both ipv4 and ipv6, the jmdns is now working with that, but jmdns needs further updates to convert fully over to the ros comms representations.
  • zeroconf_jmdns : now working rather more nicely, less multi interface confusion, but going to have to update everything else.
  • this will break everything (new comms), but jmdns is looking better.
  • zeroconf_jmdns_demos : better output.
  • zeroconf_jmdns_demos : minor demo program refactoring.
  • zeroconf_implementations : make sure we get resolving happening if a new service is found.
  • zeroconf_jmdns_demos : master browser running, but strange resolving behaviour seen by jmdns.
  • zeroconf_jmdns : added a default listener callback and api.
  • zeroconf_jmdns : listeners with userland callback handlers.
  • zeroconf_jmdns : user listener callbacks.
  • zeroconf_jmdns : toString support for the demo.
  • zeroconf_implementations : loggers so I can delete duplicating code in jmdns and android_jmdns
  • zeroconf_jmdns : comment some debug spam.
  • zeroconf_jmdns: simplify dependencies.
  • zeroconf_implementations: forgot to update the build to the standard ros template.
  • zeroconf_implementations : upgrade jmdns build method, fix android in rosinstalls.
  • zeroconf_implementations : finalise the zeroconf_overlay.rosinstall.
  • zeroconf: new overlay installer.

0.1.2 (2011-12-19)

  • zeroconf: only maintain one rosinstaller, also bypass jmdns builds if rosjava_core 0.1.0 (old) is present.
  • zeroconf_jmdns_demos : cleanup.
  • zeroconf_implementations : decided to split the jmdns stack again (for illustration).

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged zeroconf_jmdns_suite at Robotics Stack Exchange

zeroconf_jmdns_suite package from zeroconf_jmdns_suite repo

zeroconf_jmdns_suite

Package Summary

Tags No category tags.
Version 0.1.13
License Apache 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/rosjava/zeroconf_jmdns_suite.git
VCS Type git
VCS Version hydro
Last Updated 2014-03-19
Dev Status MAINTAINED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

An implementation of zeroconf in pure java.

Additional Links

Maintainers

  • Daniel Stonier

Authors

  • Daniel Stonier

Zeroconf JmDNS

This repository packages android friendly sources from the jmdns project and provides some tutorial demos.

The JmDNS Library

About

JmDNS works a little differently from avahi, although it does the same job. You can separate its functionality into two parts:

1) Zeroconf services (publishing, discovery and resolution) on a fixed, specified interface. 2) Network topology aware zeroconf services (in the author’s language - multi-homed).

What the latter means, is that it will be automatically detect what network interfaces you have and also be aware of those interfaces going up and down whilst providing a dynamic awareness of the zeroconf services that appear and disappear with those interfaces.

The network topology part of jmdns is still fairly experimental.

The Experimental Part

The network topology aware part of zeroconf is quite important. On android in particular it saves you having to worry about detecting the ip of your interface, which is rather handy. This part is quite reliable after having helped with some patches upstream.

It does have problems however handling multiple network interfaces and can also be confusing with the way it handles ipv6. I have some patches here in this code set which get it working, but either aren’t upstream yet, or probably not the proper solution yet.

Hence we have a snapshot of the sources here.

Publishing

Publishing is relatively straightforward. For ros environments, we typically only ever want or need to publish the ros master, in which case you’d publish it under something like:

_ros-master._tcp 11311

Discovery

There are two methods in the jmdns library for discovery. The first is via polling, which will always be the far more reliable method (especially if your interface is up and down alot and likely to get jmdns confused). The second is via event based listeners which give you callbacks to instantly react on a zeroconf service coming up or down.

The Ros Wrapper

I’ve got a couple of classes set up to more easily handle the jmdns library for our purposes (jmdns can be quite messy to program with). It’s not a full node, but it wouldn’t be a stretch to convert this into a full node’s functionality using zeroconf_msgs as the basis for handles that work in a similar way to the ros zeroconf_avahi package.

Tutorials

Instructions can be found in the readme in the jmdns_tutorials package.

CHANGELOG

Changelog for package zeroconf_jmdns_suite

0.1.13 (2013-11-01) ------------------* constrain open ranged dependencies.

0.1.12 (2013-10-31) ------------------* use ROS_MAVEN_REPOSITORY

0.1.11 (2013-10-25) ------------------* official maven style open ended dependencies.

0.1.10 (2013-09-23)

  • use updated ros gradle plugins with maven-publish for publishing.

0.1.9 (2013-09-22)

  • removing osgi information.

0.1.8 (2013-09-17)

  • bugfix install rule target name.
  • depend on rosjava_bootstrap for gradle plugins.
  • gradle wrapper 1.7
  • use catkin package xml version information
  • gradled, maven'd, deb'd.
  • ros-java -> rosjava migration.
  • refactoring for unique java package names.
  • fix badly copied package name for jdmns tutorial.
  • catkinization using rosjava_tools
  • demos working with new gradle build.
  • cleared out non jmdns packages.

0.1.7 (2013-04-29)

  • point at legacy rosinstallers.
  • using multiproject gradle now so we can add more projects here.
  • rosinstall file for rosjava.
  • bugfix for name in package.
  • readme added.
  • now building and installing with catkin.
  • first commit pulled in from kazuto's hg clone.
  • avahi and comms moved out.

0.1.6 (2012-07-17)

  • bugfix version bump.
  • refactored for ros code style format.
  • bugfix bad array size check, closes #35.
  • rosinstaller, use https, not git.
  • updated fuerte rosinstaller.
  • zeroconf: updated the rosinstaller for fuerte.

0.1.5 (2012-05-24)

  • updated rosdeps for rosdep2.

0.1.4 (2012-04-12)

  • Adjusting cmakelists for release into fuerte.
  • hoping to avert compilation of jmdns. Probably should divert to a separate stack.
  • new rosdeps.

0.1.3 (2012-01-04)

  • jmdns : better getInstance call.
  • jmdns: hack new jmmdns getInstance to always create, hack to trigger serviceRemoved callbacks on network down.
  • jmdns_demos : forgot to add the publisher class.
  • zeroconf_jmdns : added display names to the network interface logging.
  • jmdns : put default listener before the listener instantiation (sometimes add services will come in before it gets set otherwise).
  • zeroconf_jmdns : default listener to default discovery callback.
  • zeroconf_jmdns : now hiding all service_info api.
  • zeroconf_implementations : fix mediawiki formatting.
  • zeroconf_avahi : fix code after update to zeroconf_comms ip4/ipv6 upgrade.
  • zeroconf_jmdns: ros api utility toString function.
  • zeroconf: split the ros api to include both ipv4 and ipv6, the jmdns is now working with that, but jmdns needs further updates to convert fully over to the ros comms representations.
  • zeroconf_jmdns : now working rather more nicely, less multi interface confusion, but going to have to update everything else.
  • this will break everything (new comms), but jmdns is looking better.
  • zeroconf_jmdns_demos : better output.
  • zeroconf_jmdns_demos : minor demo program refactoring.
  • zeroconf_implementations : make sure we get resolving happening if a new service is found.
  • zeroconf_jmdns_demos : master browser running, but strange resolving behaviour seen by jmdns.
  • zeroconf_jmdns : added a default listener callback and api.
  • zeroconf_jmdns : listeners with userland callback handlers.
  • zeroconf_jmdns : user listener callbacks.
  • zeroconf_jmdns : toString support for the demo.
  • zeroconf_implementations : loggers so I can delete duplicating code in jmdns and android_jmdns
  • zeroconf_jmdns : comment some debug spam.
  • zeroconf_jmdns: simplify dependencies.
  • zeroconf_implementations: forgot to update the build to the standard ros template.
  • zeroconf_implementations : upgrade jmdns build method, fix android in rosinstalls.
  • zeroconf_implementations : finalise the zeroconf_overlay.rosinstall.
  • zeroconf: new overlay installer.

0.1.2 (2011-12-19)

  • zeroconf: only maintain one rosinstaller, also bypass jmdns builds if rosjava_core 0.1.0 (old) is present.
  • zeroconf_jmdns_demos : cleanup.
  • zeroconf_implementations : decided to split the jmdns stack again (for illustration).

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged zeroconf_jmdns_suite at Robotics Stack Exchange

zeroconf_jmdns_suite package from zeroconf_jmdns_suite repo

zeroconf_jmdns_suite

Package Summary

Tags No category tags.
Version 0.3.1
License Apache 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/rosjava/zeroconf_jmdns_suite.git
VCS Type git
VCS Version kinetic
Last Updated 2019-01-23
Dev Status MAINTAINED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

An implementation of zeroconf in pure java.

Additional Links

Maintainers

  • Daniel Stonier

Authors

  • Daniel Stonier

Zeroconf JmDNS

This repository packages android friendly sources from the jmdns project and provides some tutorial demos.

See rosjava_core readme for more information and pointers on the overall rosjava and android ecosystem.

The JmDNS Library

About

JmDNS works a little differently from avahi, although it does the same job. You can separate its functionality into two parts:

1) Zeroconf services (publishing, discovery and resolution) on a fixed, specified interface. 2) Network topology aware zeroconf services (in the author’s language - multi-homed).

What the latter means, is that it will be automatically detect what network interfaces you have and also be aware of those interfaces going up and down whilst providing a dynamic awareness of the zeroconf services that appear and disappear with those interfaces.

The network topology part of jmdns is still fairly experimental.

The Experimental Part

The network topology aware part of zeroconf is quite important. On android in particular it saves you having to worry about detecting the ip of your interface, which is rather handy. This part is quite reliable after having helped with some patches upstream.

It does have problems however handling multiple network interfaces and can also be confusing with the way it handles ipv6. I have some patches here in this code set which get it working, but either aren’t upstream yet, or probably not the proper solution yet.

Hence we have a snapshot of the sources here.

Publishing

Publishing is relatively straightforward. For ros environments, we typically only ever want or need to publish the ros master, in which case you’d publish it under something like:

_ros-master._tcp 11311

Discovery

There are two methods in the jmdns library for discovery. The first is via polling, which will always be the far more reliable method (especially if your interface is up and down alot and likely to get jmdns confused). The second is via event based listeners which give you callbacks to instantly react on a zeroconf service coming up or down.

The ROS Wrapper

I’ve got a couple of classes set up to more easily handle the jmdns library for our purposes (jmdns can be quite messy to program with). It’s not a full node, but it wouldn’t be a stretch to convert this into a full node’s functionality using zeroconf_msgs as the basis for handles that work in a similar way to the ros zeroconf_avahi package.

Tutorials

Tutorials are implemented in the jmdns_tutorials project. Instructions can be found in the zerconf_jmdns_suite package ROS wiki.

CHANGELOG

Changelog

0.3.1 (2019-01-23)

  • Updating Gradle version to 4.10.2.
  • Fixing package name for jmdns package.
  • Fix for tutorial links and testing instructions.
  • Contributors: Daniel Stonier, Juan Ignacio Ubeira, Julian Cerruti

0.3.0 (2016-12-17)

  • Updates for kinetic release.

0.2.1 (2015-02-25)

  • gradle 1.8 -> 2.2.1
  • Contributors: Daniel Stonier

0.2.0 (2015-02-18)

  • First build on indigo

0.1.13 (2013-11-01)

  • constrain open ranged dependencies.

0.1.12 (2013-10-31)

  • use ROS_MAVEN_REPOSITORY

0.1.11 (2013-10-25)

  • official maven style open ended dependencies.

0.1.10 (2013-09-23)

  • use updated ros gradle plugins with maven-publish for publishing.

0.1.9 (2013-09-22)

  • removing osgi information.

0.1.8 (2013-09-17)

  • bugfix install rule target name.
  • depend on rosjava_bootstrap for gradle plugins.
  • gradle wrapper 1.7
  • use catkin package xml version information
  • gradled, maven'd, deb'd.
  • ros-java -> rosjava migration.
  • refactoring for unique java package names.
  • fix badly copied package name for jdmns tutorial.
  • catkinization using rosjava_tools
  • demos working with new gradle build.
  • cleared out non jmdns packages.

0.1.7 (2013-04-29)

  • point at legacy rosinstallers.
  • using multiproject gradle now so we can add more projects here.
  • rosinstall file for rosjava.
  • bugfix for name in package.
  • readme added.
  • now building and installing with catkin.
  • first commit pulled in from kazuto's hg clone.
  • avahi and comms moved out.

0.1.6 (2012-07-17)

  • bugfix version bump.
  • refactored for ros code style format.
  • bugfix bad array size check, closes #35.
  • rosinstaller, use https, not git.
  • updated fuerte rosinstaller.
  • zeroconf: updated the rosinstaller for fuerte.

0.1.5 (2012-05-24)

  • updated rosdeps for rosdep2.

0.1.4 (2012-04-12)

  • Adjusting cmakelists for release into fuerte.
  • hoping to avert compilation of jmdns. Probably should divert to a separate stack.
  • new rosdeps.

0.1.3 (2012-01-04)

  • jmdns : better getInstance call.
  • jmdns: hack new jmmdns getInstance to always create, hack to trigger serviceRemoved callbacks on network down.
  • jmdns_demos : forgot to add the publisher class.
  • zeroconf_jmdns : added display names to the network interface logging.
  • jmdns : put default listener before the listener instantiation (sometimes add services will come in before it gets set otherwise).
  • zeroconf_jmdns : default listener to default discovery callback.
  • zeroconf_jmdns : now hiding all service_info api.
  • zeroconf_implementations : fix mediawiki formatting.
  • zeroconf_avahi : fix code after update to zeroconf_comms ip4/ipv6 upgrade.
  • zeroconf_jmdns: ros api utility toString function.
  • zeroconf: split the ros api to include both ipv4 and ipv6, the jmdns is now working with that, but jmdns needs further updates to convert fully over to the ros comms representations.
  • zeroconf_jmdns : now working rather more nicely, less multi interface confusion, but going to have to update everything else.
  • this will break everything (new comms), but jmdns is looking better.
  • zeroconf_jmdns_demos : better output.
  • zeroconf_jmdns_demos : minor demo program refactoring.
  • zeroconf_implementations : make sure we get resolving happening if a new service is found.
  • zeroconf_jmdns_demos : master browser running, but strange resolving behaviour seen by jmdns.
  • zeroconf_jmdns : added a default listener callback and api.
  • zeroconf_jmdns : listeners with userland callback handlers.
  • zeroconf_jmdns : user listener callbacks.
  • zeroconf_jmdns : toString support for the demo.
  • zeroconf_implementations : loggers so I can delete duplicating code in jmdns and android_jmdns
  • zeroconf_jmdns : comment some debug spam.
  • zeroconf_jmdns: simplify dependencies.
  • zeroconf_implementations: forgot to update the build to the standard ros template.
  • zeroconf_implementations : upgrade jmdns build method, fix android in rosinstalls.
  • zeroconf_implementations : finalise the zeroconf_overlay.rosinstall.
  • zeroconf: new overlay installer.

0.1.2 (2011-12-19)

  • zeroconf: only maintain one rosinstaller, also bypass jmdns builds if rosjava_core 0.1.0 (old) is present.
  • zeroconf_jmdns_demos : cleanup.
  • zeroconf_implementations : decided to split the jmdns stack again (for illustration).

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Name Deps
rosjava

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged zeroconf_jmdns_suite at Robotics Stack Exchange