[zeromq-dev] majordomo protocol; frame 0

[Pieter Hintjens]

Hi Chuck,

> I am working on a new protocol to be published on the unprotocols.org site. I am following the template as given by the majordomo protocol [1]. One thing about the protocol definition bothers me.

I'd suggest the rfc.zeromq.org site.

> All of the message types define frame0 as a null message part. The assumption is that this protocol only makes sense with REQ/XREQ sockets which always send a null message part first. So the part that bothers me is that the *socket framing* is part of the majordomo protocol definition.
>
> Why is that necessary? If an implementer is using a REQ socket, they get that frame "for free" and never even see it. If they use XREQ, then they must know to prepend all of their messages with a null part anyway.

Do you mean in MDP/Client or MDP/Worker? In the client protocol it's
pretty clearly stated how the empty frame works. In the worker
protocol the empty frame is added to allow multiple hops. It wasn't in
initial versions, and IMO could be dropped.

-Pieter