54a9e44d21
- Implement nanomsg multipart with MessagePack. - Use the MessagePack from FairSoft and handle not found case. - Update splitter, merger and proxy devices to handle multi-part. - Let FairMQParts.At() return pointer reference (can be used for moving). - Add missing const specifier in the message interface. - Add transmit kernel size setting to channels (ZMQ_SNDBUF). - Remove FairMQBuffer device. - Remove old multi-part methods from Tutorial3 example (to be replaced with Parts API). - Make callback mandatory for newMsg(data, size, callback). - Add missing <vector> include in FairMQSocket. |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| ex8-multipart.json | ||
| FairMQExample8Sampler.cxx | ||
| FairMQExample8Sampler.h | ||
| FairMQExample8Sink.cxx | ||
| FairMQExample8Sink.h | ||
| README.md | ||
| runExample8Sampler.cxx | ||
| runExample8Sink.cxx | ||
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.