This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
info:zeromq [2014-06-24 22:59] sam [General Notes] |
info:zeromq [2014-08-20 16:49] (current) sam [Integrating with Event Loops] |
||
---|---|---|---|
Line 24: | Line 24: | ||
* Apparently Ansible uses [[http://www.keyczar.org/|Keyczar]] to help add security to its ZeroMQ-based "Fireball" mode | * Apparently Ansible uses [[http://www.keyczar.org/|Keyczar]] to help add security to its ZeroMQ-based "Fireball" mode | ||
===== Integrating with Event Loops ===== | ===== Integrating with Event Loops ===== | ||
- | There is some trickiness because of the edge-triggering. Example integration with libev: http://funcptr.net/2013/04/20/embedding-zeromq-in-the-libev-event-loop/ | + | There is some trickiness because of the edge-triggering. Example integration with libev: http://funcptr.net/2013/04/20/embedding-zeromq-in-the-libev-event-loop/. Another small example is at http://stackoverflow.com/a/10861503. |
For integration with Qt, QSocketNotifier provides monitoring of file descriptors, and a QTimer with a timeout of 0 should act be the same as the idle callback mentioned in the article. There is a C++ implementation of this in [[https://github.com/jonnydee/nzmqt]]. For Python it seems like it would be better to re-implement with PyQt. | For integration with Qt, QSocketNotifier provides monitoring of file descriptors, and a QTimer with a timeout of 0 should act be the same as the idle callback mentioned in the article. There is a C++ implementation of this in [[https://github.com/jonnydee/nzmqt]]. For Python it seems like it would be better to re-implement with PyQt. | ||
+ | |||
====== From the Guide ====== | ====== From the Guide ====== | ||
===== Anecdotes ===== | ===== Anecdotes ===== |