[zeromq-dev] Malamute broker project

Doron Somech somdoron at gmail.com
Sun Mar 1 17:52:53 CET 2015

So I went over the code, really liked it. Very simple.

I have a question regarding services, for each stream you are using a
dedicate thread (actors) and one thread for managing mailboxes. However (if
I understood correctly) for services you are doing the processing inside
the server thread, why didn't you use an actor for each service or actor to
manage all services? I think the matching of services can be expensive and
block the main thread.

On Fri, Feb 27, 2015 at 12:21 PM, Pieter Hintjens <ph at imatix.com> wrote:

> Hi all,
> I've moved the Malamute broker project into the ZeroMQ organization on
> GitHub, it's now at https://github.com/zeromq/malamute.
> There is a whitepaper explaining the goals:
> https://github.com/zeromq/malamute/blob/master/MALAMUTE.md
> The broker is already production ready, with transient messaging only
> (no persistence). If you'd like help using this in your projects, or
> integrating it into your products, please contact me. License is
> MPLv2.
> -
> Pieter Hintjens
> iMatix
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150301/dcf8eab0/attachment.htm>

More information about the zeromq-dev mailing list