[zeromq-dev] Question: release policies and v3.x

Pieter Hintjens ph at imatix.com
Mon Jul 18 21:00:51 CEST 2011


On Mon, Jul 18, 2011 at 8:32 PM, Marcus Cavanaugh
<marcus at gameclosure.com> wrote:

> Our use case for ZMQ_IDENTITY is this: We have a few stateful backend
> services that need to communicate with other servers. We need to direct
> requests to specific services, so round-robin balancing doesn't work. (We
> can't easily make those services stateless.) We use router sockets for that.
> I'm not sure that there's an easy way to do that without ZMQ_IDENTITY.
> Whenever we need messages to go to a specific machine, round-robin load
> balancing doesn't do what we need.

With router sockets you can address specific servers, once these have
identified themselves. The usual model is to have an authentication
step, then use the authenticated user id for routing. This doesn't
require explicit identities. Does that sound like it would work for
you?

E.g.

Client: OHAI + username + password
Server: OHAI-OK + server info / WTF + reason

-Pieter



More information about the zeromq-dev mailing list