[zeromq-dev] Devices and config files

[gonzalo diethelm]

> > 1. How will one use this from other languages (Python, Java, etc.)?
> 
> There are JSON parsers in every language, see www.json.org.

I was afraid this would be your answer... I am aware it is not an easy
question: should the basic C library provide everything needed by all
the bindings (including the ability to read configuration files)?

> > 2. I would love to be able to have a configuration file where I can
put
> > together the whole network architecture of my distributed
application.
> 
> Sounds right.  I was thinking of a config broker that distributes
> these config files to nodes as they start up... so the broker is the
> only fixed endpoint in the network.
> 
> > It would be AWESOME if we could accommodate this type of
configuration
> > in a way that's amenable to be used from any 0MQ binding. It would
be
> > even better if I could create standard 0MQ devices using something
like
> > this.
> 
> +1

Let me clarify one thing, though: by "device" I am referring to "a
bucket of sockets". As I mentioned before, one of my devices would have:

* A REP socket for synchronous queries.
* A PULL socket for pipelined processing.
* A PUB socket for publishing management stats.
* A SUB socket for receiving management commands.
* etc.

I would love to be able to specify all these as the pieces forming my
very unique device. And perhaps the device class would be abstract, with
the proper plugins (methods) that I would have to override in order to
wire my device the way I need it.

-- 
Gonzalo Diethelm