Michael Schubert

+1 for `ZMQ_NOTIFY_ROUTER`

Looking at this again after a long time, I think providing a `ParallelCluster` backend for `clustermq` workers is not straightforward. The reason for this is that, as @HenrikBengtsson said, the...

The `*LB` methods should be fine, but I don't see a way to support `clusterCall` or `clusterEvalQ`. [The docs](https://stat.ethz.ch/R-manual/R-patched/library/parallel/html/clusterApply.html) suggest to use those to load libraries on the nodes, which...

Relevant: https://bugs.r-project.org/show_bug.cgi?id=18587

No longer relevant with the `v0.9` rewrite because any objects can be added to the worker environment (and none are required)

Solution to this will be a consequence of #119

I think I fixed this now, if not please reopen

Great catch @luwidmer, that return statement indeed looks off! Note that it's fixed in [`develop`](https://github.com/mschubert/clustermq/blob/develop/src/CMQMaster.h#L24), but happy to merge a PR if you don't want to wait for that

Making the port range configurable via an option makes sense, but I'm not sure I see the advantage of using `parallely::freePort`?

This is now implemented from 0aa0e4ab44b69a4a9a0fd85455e93c22550c5677 on: ```r w = workers(3) w$recv() w$info() #