[zeromq-dev] Monitoring and management question
Hello. First of all, thank for reading and congratulations for ZMQ. We are considering using ZMQ to implement a communication library for all our applications, which are almost always distributed. We make telephonic applications. All our clients require us to inform, usually through SNMP, the state of all the links that the application establishes. ZMQ has non connected protocols, which is good. But we also need information about the visibility of the remote peers. The question is: Is there any plan to add some observability to ZMQ library? Something like a getsockopt that list the visibility state of the endpoints the socket is connected to? Thank in advance. Juan Carlos Franzoy Licenciado en Sistemas ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Monitoring and management question
2010/12/21 Steven McCoy steven.mc...@miru.hk On 21 December 2010 21:12, Juan Carlos Franzoy jfran...@gmail.com wrote: Is there any plan to add some observability to ZMQ library? Something like a getsockopt that list the visibility state of the endpoints the socket is connected to? The general reply is that 0mq is a messaging middleware not a streaming middleware, therefore there is no link state. You could technically have an equivalent to Linux netlink sockets providing link layer notifications as a workaround. The more useful statistic would be to have a decaying indicator of last response from each peer. http://en.wikipedia.org/wiki/Netlink I understand it is a messaging middleware, but wouldn't it be a good thing if you can monitor the state of the middleware? : - state of connection - visibility of peers - occupation of internal queues - any other already known data ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
[zeromq-dev] Newbie question
Hello everybody. First of all, thanks for reading my post, and please forgive me if this is not the correct place to ask this question. We have developed a portable communication API for our applications. We are evaluating implement it using AMQP, DDS, ØMQ or, well, doing it from scratch. I am enthusiastic about 0MQ for this task. In the ØMQ documentation it says Each ØMQ socket belonging to a particular *context* may only be used by *the thread that created it*. This a very strong limitation for us. Because our clients (the application who will user the library) may have no control of threads, perhaps they run in a thread pool provided by another framework. I wanted to ask why this restriction exists. In the future, can we have a socketopt or a new socket type to overcome it? Thanks in advance. -- Juan Carlos Franzoy Licenciado en Sistemas ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
