[zeromq-dev] Majordomo handling malformed messages

Pieter Hintjens ph at imatix.com
Fri Dec 12 12:19:46 CET 2014

We do need to make a new RFC, as the code has gone beyond RFC 18.

It's worth making the broker more robust, if you are using it.

On Fri, Dec 12, 2014 at 10:05 AM, Lucas Russo <lerwys at gmail.com> wrote:
> Hello Everyone,
> I'm using the majordomo protocol to do a service-based thread lookup,
> sharing the same context among all threads.
> I would like to make the reference majordomo implementation
> (https://github.com/zeromq/majordomo/) a little bit more robust against
> malformed messages. Right now, if any of the parts (client, broker or
> worker) receive a wrong message format, it will just crash with the asserts
> being used or not check the message whatsoever.
> So, if you think this is a valid putting a little effort on, I would like to
> ask for suggestions on how to do that.
> First of all, maybe the majordomo protocol (http://rfc.zeromq.org/spec:18)
> would need to be changed, as the worker and/or broker does not send an error
> message back to the client in response to a malformed message received.
> Second, with the modification in the protocol, the work would be just to
> remove the asserts and replace them with proper checking and error messages
> back to the client.
> Do you guys think this would make a good improvement for the Majordomo
> protocol and reference implementation?
> Also, I know about the Malamute intent to be a "general" messaging protocol,
> but does it replace Majordomo?
> Regards,
> Lucas
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list