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

[Vineet Jain]

>> Good. My preference would be to create a global_queue in admin_client and let app1 and app2 bind to it (see p1.png).

However the admin client is just a client running on the admin's
laptop. It is not a long running process so that will not work.

>>If you except your logger to go offline or crash (do you?) you have to create a separate queue process (see p2.png). 'chatroom' application is actually a queue process. You can use it straight away, just discard the code that adds timestamps to the messages.

Yes. The loggers can go down for maintainance or can also crash (less
frequenetly I hope). So I do need a seperate process that would (as in
p2.png) . The problem is that the chatroom app needs to know before
hand the queues it's going to listne to. In my case I'm hopping not to
have to chage the queue process. Your example is simplified in that
there is only one global queue. However, if I want to have a seperate
global queue for each python logger, can the python logger process
create a global queue in the queue process? or can the queue process
only create and delete global queues in its own process?

It's not a big deal, but it would be easier for a new person to get
started if zmq_server (or something similar) could be the host for
queues and exchanges out of the box. Then in my example, app1 and app2
would create two global queues on this central queue process and the
admin client would just connect to it when needed. Is this not a
common use case?

>> Yes, that's the default. If there's no queue bound to an exchange, messages are discarded.

Ok thanks.