service-discovery

I can't resolve one service while another is being resolved? If that's what the error means... What is the way to wait until it is resolved? @Override public void onServiceFound(NsdServiceInfo service) { Log.d(TAG, "Service found. " + service); if (service.getServiceType().equals(SERVICE_TYPE)) { if (service.getServiceName().contains(mServiceName)) { mNsdManager.resolveService(service, mResolveListener); } } } java.lang.IllegalArgumentException: listener already in use at android.net.nsd.NsdManager.resolveService(NsdManager.java:613) at com.example.miguel.broadcast.LocalService$2

Recently several service discovery tools have become popular/"mainstream", and I’m wondering under what primary use cases one should employ them instead of traditional load balancers. With LBs, you cluster a bunch of nodes behind the balancer, and then clients make requests to the balancer, who then (typically) round robins those requests to all the nodes in the cluster. With service discovery ( Consul , ZK , etc.), you let a centralized “consensus” service determine what nodes for particular service are healthy, and your app connects to the nodes that the service deems as being healthy. So

I have an Android app that I had working a few months ago which I could use to connect my Droid X2 to an ASUS Transformer tablet over Bluetooth. That connection worked fine. I just finished coding client/server pairs using PyBlueZ on a couple Ubuntu machines, and an analogous client/server pair using BlueCove on a Windows machine. I thought it would be a breeze to take these three working, tested systems and connect them. Unfortunately, I am currently unable to connect my Droid X2 to my other machines, nor can I connect my other machines to my Droid X2 (I no longer have the ASUS Transformer).

I am having problem understanding the need of a separated service discovery server while we could register the slave node to the master node at the slave node start-up through whatever protocol. Hosting another service seem redundant to me. VonC Docker Swarm is there to create a cluster of hosts running Docker and schedule containers across the cluster. It does not include service discovery , which is provided by a backend service, such as etcd, consul or zookeeper. The first problem: service registration and discovery is an infrastructure concern, not an application concern. The second

During the first implementation of the NSDManager using the examples and the tutorial on the developer page , the application successfully started the discovery and found the devices. However now it seems to be broken... When the program is started, after some initialization, the code enters the following method and successfully run: public void discoverServices() { Log.d(TAG, "Initializing discovery on NSD"); mNsdManager.discoverServices( SERVICE_TYPE, NsdManager.PROTOCOL_DNS_SD, mDiscoveryListener); } The log-message is received. After a good while (say approx 5 mins.) this is outputted from