UUID

[DRTEK]

hello
is it possible to set uuid at runtime ?
thanks

[bluca]

No as it's used to identify a peer by all other nodes, so it would become a bit messy. What's your use case?

[DRTEK]

i have central database holds peers ,i could use the name as identifier however i wanted to see if it was doable .

[sappo]

You could set a custom identifier in the headers which are provided by each ENTER messages. Am 11.03.2017 22:28 schrieb "MK" <notifications@github.com>:

…

i have central database holds peers ,i could use the name as identifier however i wanted to see if it was doable . — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#526 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAeGuqEZqoWahW7JCQeM5SN3m_tlz7V4ks5rkxHtgaJpZM4MaVW9> .

[DRTEK]

yes i think it is right way to go
thanks

[bluca]

Cool. Closing now since it's solved.

[wesyoung]

fwiw, i've tried something like this in the past- the lesson learned? don't try to track/set uuid's. it just gets messy. we ended up using the HEADER for something like that. seemed to work ok. we augmented it a little with a local routing table in the peer that held node names (which i think may have been overkill, but we were learning the framework and messing around a bit).

[sappo]

@DRTEK not sure if this helps in your case, but zyre allows you to set the public name of its node. Which is the first 6 characters of the uuid by default. The problem was that the API call to set this name (set_name()) was not exposed in the header file until now.

PR #527 fixes this!

[DRTEK]

sure it does 👍 thank you very much ..
if i may i have one more question (sorry i do not know where to ask questions about the library )

• is it okay to pass the zactor_t as an argument to different threads so main and another thread can send messages to the thread ? (please see below)

  zactor_t *cluster_actor = zactor_new(createnode, clusternode);

  zactor_t *wireless_actor = zactor_new(startwilo, cluster_actor);
  thanks alot

[bluca]

no, actors (and zmq sockets) must not be passed among threads

[DRTEK]

can you point me to two way communication sample between threads ? please

[bluca]

a zmq socket of type ZMQ_PAIR and endpoint inproc://