Video Introduction to ØMQ
Oliver Smith has produced this lovely video explaining ØMQ and showing off its main features, live:
Comments: 3
Written: 1280152964|%Y.%m.%e
Revised: 1280161097|%Y.%m.%e
If you found this page useful, please rate it up so others will find it.
Edit this page | Tags | Print
See also
- A multithreaded server in 10 mins
- Berlin Buzzwords 2010
- Building a GeoIP server with ZeroMQ
- Building ØMQ and pyzmq on Red Hat
- Few Blogposts on ØMQ
- Historical Highlights
- Installing ZeroMQ and Java bindings on Ubunu 10.10
- Internet Worldview in Messaging World
- Load Balancing In Java
- Loggly Switches to ØMQ
- Message Oriented Network Programming
- Mongrel2 Is "Self-Hosting"
- Multithreading Magic
- New - ØMQ Labs!
- Not To Be Confused
- ØMQ/2.0.6 on OpenVMS
- ØMQ/2.0.7 (beta) released
- ØMQ/2.1.0 available on OpenVMS
- ØMQ And QuickFIX
- ØMQ available at CPAN
- ØMQ blog by Gerard Toonstra
- ØMQ for Clojure
- ØMQ - The Game
- Python Multiprocessing With ØMQ
- RFC: ØMQ Contributions, Copyrights and Control
- Ruby Gem for ØMQ/2.0.7 available!
- September Meetups
- The Long and Winding Road Behind
- To Trie or not to Trie
- Welcome, Objective-C :-)
- Zero-copy and Multi-part Messages
- ZeroMQ and Clojure, a brief introduction
- ZeroMQ an introduction
- ZeroMQ: Modern & Fast Networking Stack
- ZeroMQ: What You Need to Know Braindump
Who's watching this page?
... and more
page revision: 3, last edited: 26 Jul 2010 16:18
Shouldn't downstream be the socket receiving and upstream the one sending?
Like a river flows from upstream to downstream
It is a common confusion due to the opposing perspective of the river vs. the swimmer, and that's why we renamed the sockets to PULL and PUSH.
Portfolio
The naming is confusing. It actually means "get messages from upstream" and "send message downstream". In the 2.0.8 release the socket types were renamed to PUSH and PULL respectivelly, which is unambiguous. DOWNSTREAM and UPSTREAM still exist for backward compatibility reasons.