As I can see, this solution is generally applicable, but I’m not sure we need
all it’s features with e.g. rabbitmq as it also has it’s own means of
authentication and support for ssl. For zmq it is one of recommended backends.
> On Mar 25, 2016, at 18:39, Joshua Harlow
Out of curiosity for this, is it a generally applicable solution that
could also be used for the other in(secure) messaging issues that have
been talked about in:
http://lists.openstack.org/pipermail/openstack-dev/2016-March/thread.html#90082
On 03/25/2016 05:28 AM, Oleksii Zamiatin wrote:
Hi everyone!
Here is the status update for zmq driver upstream development in M and plans
for N
What was done:
1. Dedicated patterns usage was finally impelemented. DEALER/ROUTER for CALL,
PUSH/PULL for CAST, PUB/SUB for fanout.
Last time everything worked over DEAL/ROUTER which was