ffbe90b638
- require DDS 2.2 - fix regressions in automatic port binding - fix regression in channel API - update DDS example readme |
||
|---|---|---|
| .. | ||
| 1-1 | ||
| 1-n-1 | ||
| builtin-devices | ||
| copypush | ||
| dds | ||
| multipart | ||
| multiple-channels | ||
| multiple-transports | ||
| region | ||
| req-rep | ||
| CMakeLists.txt | ||
| README.md | ||
FairMQ Examples
Set of FairMQ examples. More examples that combine FairMQ with FairRoot can be found in the FairRoot repository.
1-1
A simple topology of two devices - Sampler and Sink. Sampler sends data to Sink with the PUSH-PULL pattern.
1-n-1
A simple topology of three device types - Sampler, Processor and Sink. Sampler sends data to one or more Processors, who modify the data and send it to one Sink. Transport with the PUSH-PULL pattern. The example also shows the configuration via JSON files, as oposed to --channel-config that is used by other examples.
DDS
This example demonstrates usage of the Dynamic Deployment System (DDS) to dynamically deploy and configure a topology of devices. The topology is similar to those of Example 2, but now it can be easily distributed on different computing nodes without the need for manual reconfiguration of the devices.
Copy & Push
A topology consisting of one Sampler and two Sinks. The Sampler uses the Copy method to send the same data to both sinks with the PUSH-PULL pattern. In countrary to the PUB-SUB pattern, this ensures that all receivers are connected and no data is lost, but requires additional channels to be configured.
Request & Reply
This topology contains two devices that communicate with each other via the REQ-REP pettern. Bidirectional communication via a single socket.
Multiple Channels
This example demonstrates how to work with multiple channels and multiplex between them.
Sending Multipart messages
This example shows how to send a multipart message from one device to the other. (two parts message parts - header and body).
Multiple Transports example
This examples shows how to combine different channel transports (zeromq/nanomsg/shmem) inside of one device and/or topology.
Region example
This example demonstrates the use of a more advanced feature - UnmanagedRegion, that can be used to create a buffer through one of FairMQ transports. The contents of this buffer are managed by the user, who can also create messages out of sub-buffers of the created buffer. Such feature can be interesting in environments that have special requirements by the hardware that writes the data, to keep the transfer efficient (e.g. shared memory).