[zeromq-dev] Questions
Stam, Louis van der - Acision
louis.van.der.stam at acision.com
Wed Nov 26 07:36:26 CET 2008
Hi,
I have recently found my way to the zeromq web-site and have been studying the API and the examples.
Not everything is clear to me, so that is why I come here and post some questions:
- It's my understanding that the threads that have to be associated with a poll_thread_t instance are there only for the purpose of dealing with IPC (between different processes). They do not serve a purpose when exchanging messages between an exchange and a queue inside the same process. Is this a correct view?
- It's my understanding that the poll_thread_t instances are not counted as a thread in the sense of the number of threads supported by the dispatcher instance. Is this a correct view?
- It's my understanding that a thread associates itself with the dispatcher through the api_thread_t instance and that it is this association that counts in the sense of the number of threads supported by the dispatcher. Is this a correct view?
- I'm having similar thoughts on the use of the threads associated with a binding as for the poll_thread_t. Is this a correct view?
- Is it possible to have one thread listen to two or more queues queues?
- Is it possible to have one thread listen to a queue (or more see above) and also get woken-up when a fd has some work to be done (like a socket fd)?
- Is it possible to get a notification when a binding is established, and if so is it possible to see which exchange is binding to what queue?
- Is it possible to get a notification of a binding being broken, and if so is it possible to see which exchange is unbound from what queue?
Seeing the above it's quite a list already.
Looking forward to your answers. Regards,
Louis van der Stam
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
More information about the zeromq-dev
mailing list