Closed fieldOfView closed 9 years ago
You should request peer names though pyre. Now that I'm looking at it I think this method might be missing. You can do get_peers() and from that you should do get_name(uuid). I have to check with zyre.
It does not look like get_name() takes an argument; it only returns the name of the node itself (not its peers).
So the reply from the zmq devs was that you should track names yourself as you already receive them through the ENTER event. So this is not going to happen in Pyre either.
Ok, I'll continue using that workaround.
Since the recent Pyre update, peer names are no longer stored in the capability tree. Instead, names live in the Pyre land, and are sent with all messages.
There are still usecases where it is useful to be able to know the name of a peer, for example when compiling a list of all current peers in the network (and presenting this to the user in a friendlier way than though the uuids).
Perhaps if names do not belong in the capability-tree (ie: stored in
peers_capabilities
), there could be apeers_names
dict?