3e013f98b8
* accept ZEROMQ_ROOT as env or cmake variable to hint at install
location (used by aliBuild/alienv)
* added more docs
* fixed mismatch between module name ZeroMQ and prefix of
generated variables ZMQ -> ZeroMQ is now the preferred prefix
(old variables are still available and marked deprecated)
* the aliBuild zeromq recipe does not install zmq.hpp header,
so the module searches now for the zmq.h header
(which is anyways the only one we use)
* some cosmetic changes
* add option ZeroMQ_NO_DEPRECATION to suppress deprecation warning
|
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| ex8-multipart-multiple-endpoints.json | ||
| ex8-multipart.json | ||
| FairMQEx8Header.h | ||
| FairMQExample8Sampler.cxx | ||
| FairMQExample8Sampler.h | ||
| FairMQExample8Sink.cxx | ||
| FairMQExample8Sink.h | ||
| README.md | ||
| runExample8Sampler.cxx | ||
| runExample8Sink.cxx | ||
| startMQEx8.sh.in | ||
Example 8: Sending Multipart messages
A topology of two devices - Sampler and Sink, communicating with PUSH-PULL pattern.
The Sampler sends a multipart message to the Sink, consisting of two message parts - header and body.
Each message part is a regular FairMQMessage. To combine them into a multi-part message, simply send all but the last part with SendPart() and the last part with Send() as shown in the example.
The ZeroMQ transport guarantees delivery of both parts together. Meaning that when the Receive call of the Sink receives the first part, following parts have arrived too.
The header contains a simple data structure with one integer. The integer in this structure is used as a stop flag for the sink. As long as its value is 0, the Sink will keep processing the data. Once its value is 1, the Sink will exit its Run() method.