[zeromq-dev] Ideas for a zfork class

[Rodrigo Mosconi]

Hi all,

I use a lot zthreads (I know that it`s deprecated, but I can`t change to
zactor now) on a project.  But for some external reasons, I need to fork
some zmq worker and I would like to manage this fork like zthread/zactor.
Let`s call it zfork, and I would like to exchange some thoughts before
start developing it.

Some aspects that I already toughed:

1 - master/worker intercomunication can`t rely on ZMQ_PAIR socket; maybe a
ROUTER/DEALER over IPC approach could be better.
2 - The master could generate a identification for the slave
3 - presence of some sort of heart-beating
4 - the master may act like a broker over the "control/parent-child" zsocket
5 - if over IPC, the master could set filters (ZMQ_IPC_FILTER_...) on the
socket

Any other ideas or comments?

Mosconi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140902/3561f7c5/attachment.htm>