[zeromq-dev] Asynchronous Client-Server Pattern in ZGuide

[Ilja Golshtein]

Hello,
Pieter,
All.

In ZGuide in "The Asynchronous Client-Server Pattern" section we have
==
Workers get unaddressed messages, and we manage the connections from server thread to worker threads explicitly using a ROUTER socket as backend. This would require that workers start by telling the server they exist, which can then route requests to workers and track which client is 'connected' to which worker. This is the load-balancing pattern again.
==

Since we are talking about Routers at workers' side, I am not sure why "This would require that workers start by telling the server they exist". 
It is server who should start a communication and he does it anyway.

Actually switching from DEALER to ROUTER at worker's side requires reading and writing extra frame, which is identity.

Do I miss something?

Thanks.



-- 
Best regards
Ilja Golshtein