[zeromq-dev] Just installed zmq and have a question about wiring and running a broker.

Martin Sustrik sustrik at fastmq.com
Tue Apr 7 15:47:45 CEST 2009

Hi Vineet,

Currently, the chatroom and zmq_server have to be separate processes. 
However, as quite a lot of people complained about this restriction, we 
would like to introduce two separate messaging models in post-0.6 future.

The idea is that there'll be layer 1 API ("0MQ sockets") that would 
basically work as POSIX sockets adding all the fancy stuff: 
message-orientation, high performance, queueing, different transport 
protocols, multicast, load balancing, on-disk offload, auto-reconnect, 
wide OS and language support etc. No zmq_server and no symbolic name 
resolving at layer 1:

int s = zmq::socket ();
zmq::bind (s, "zmq.tcp://");
message_t msg;
zmq::receive (&msg);


int s = zmq::socket ();
zmq::connect (s, "zmq.tcp://");
message_t msg (data, size);
zmq::send (s, msg);

Then there'll be layer 2 API ("0MQ for enterprise") with current API, 
zmq_server, symbolic name resolving, configuration stored in a directory 
service etc.

I expect there are several people on the mailing list who would benefit 
from "0MQ sockets". If so, let us know your requirements and use cases 
so that we can incorporate it into the design early on. Also, any help 
with design and/or implementation would be welcome.


Vineet Jain wrote:
> I'm working with the python library and looked at the Chat Application.
> Can the chat application be setup so that the zmq_server actually
> hosts the exchange and queue? I want the chat server, the prompt and
> display to not only use the zmq_server for directory services but also
> be source for messages and the queue to push messages to.
> _______________________________________________
> 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