![]() Like a favorite dish, ZeroMQ sockets are easy to digest. It turns “Message Oriented Middleware”, a phrase guaranteed to send the whole room off to Catatonia, into “Extra Spicy Sockets!”, which leaves us with a strange craving for pizza and a desire to know more. Kudos to Martin Sustrik for pulling this off. One thing that makes ZeroMQ especially tasty to developers is that it uses sockets and messages instead of some other arbitrary set of concepts. Sockets are the de facto standard API for network programming, as well as being useful for stopping your eyes from falling onto your cheeks. However, the result will slowly fix your world view about how to design and write distributed software. ZeroMQ presents a familiar socket-based API, which requires great effort for us to hide a bunch of message-processing engines. It’s for your own good and it hurts us more than it hurts you. ![]() To be perfectly honest, ZeroMQ does a kind of switch-and-bait on you, for which we don’t apologize. Using the HWM (high-water mark) to protect against memory overflows.How to create and use message envelopes for pub-sub.How to use ZeroMQ to coordinate a network of nodes.How to use ZeroMQ to signal between threads.How to write multithreaded applications with ZeroMQ.How to build a simple message queuing broker.How to forward messages across networks.How to send and receive multipart messages.How to check a ZeroMQ application for memory leaks.How to shut down a ZeroMQ application cleanly.How to handle interrupt signals like Ctrl-C.How to handle fatal and nonfatal errors properly.How to handle multiple sockets in one thread.How to build your apps around ZeroMQ’s asynchronous I/O model. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |