FairMQ/examples/multipart
2019-10-29 20:06:31 +01:00
..
CMakeLists.txt Include empty parts in multipart example/test 2019-10-29 20:06:31 +01:00
ex-multipart-multiple-endpoints.json Refactor the examples after move from FairRoot 2018-05-02 16:12:57 +02:00
fairmq-start-ex-multipart.sh.in Include empty parts in multipart example/test 2019-10-29 20:06:31 +01:00
Header.h Refactor the examples after move from FairRoot 2018-05-02 16:12:57 +02:00
README.md Update example READMEs 2018-05-02 16:12:57 +02:00
runSampler.cxx Add config plugin class. 2019-07-10 19:35:18 +02:00
runSink.cxx Add config plugin class. 2019-07-10 19:35:18 +02:00
Sampler.cxx Include empty parts in multipart example/test 2019-10-29 20:06:31 +01:00
Sampler.h Formatting, some refactoring 2019-10-29 20:06:31 +01:00
Sink.cxx Include empty parts in multipart example/test 2019-10-29 20:06:31 +01:00
Sink.h Formatting, some refactoring 2019-10-29 20:06:31 +01:00
test-ex-multipart.sh.in Run multipart example with ofi 2019-03-21 18:03:32 +01:00

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 use FairMQParts. Add messages to FairMQParts with AddPart method.

All parts are guaranteed to be delivered together. The Receive call in the sink will recive the entire parts structure.

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 data handler method of the Sink will return false, which will exit the RUNNING state of the device.