flâneur

2. Sockets and Patterns | ØMQ - The Guide

zguide.zeromq.org · 59,207 words · saved by 1 readers

In Chapter 1 - Basics we took ZeroMQ for a drive, with some basic examples of the main ZeroMQ patterns: request-reply, pub-sub, and pipeline. In this chapter, we’re going to get our hands dirty and start to learn how to use these tools in real programs. We’ll cover: To be perfectly honest, ZeroMQ does a kind of switch-and-bait on you, for which we don’t apologize. It’s for your own good and it hurts us more than it hurts you. ZeroMQ presents a familiar socket-based API, which requires great effort for us to hide a bunch of message-processing engines. However, the result will slowly fix your world view about how to design and write distributed software. Sockets are the de facto standard API for network programming, as well as being useful for stopping your eyes from falling onto your cheeks. One thing that makes ZeroMQ especially tasty to developers is that it uses sockets and messages instead of some other arbitrary set of concepts. Kudos to Martin Sustrik for pulling this off. It turn

Chapter 2 - Sockets and Patterns # In Chapter 1 - Basics we took ZeroMQ for a drive, with some basic examples of the main ZeroMQ patterns: request-reply, pub-sub, and pipeline. In this chapter, we're going to get our hands dirty and start to learn how to use these tools in real programs. We'll cover: How to create and work with ZeroMQ sockets. How to send and receive messages on sockets. How to build your apps around ZeroMQ's asynchronous I/O model. How to handle multiple sockets in one thread. How to handle fatal and nonfatal errors properly. How to handle interrupt signals like Ctrl-C. How t

related reading