Mirror/FairMQ
1
0
Fork 0
mirror of https://github.com/FairRootGroup/FairMQ.git synced 2025-10-13 16:46:47 +00:00
Code Issues Packages Projects Releases Wiki Activity
efd6523112
FairMQ/examples/n-m
History
Dennis Klein efd6523112 feat(Parts)!: Refine and tweak 
* Optimize appending another Parts container
* Remove redundant/verbose comments
* Change r-value args to move-only types into l-value args for
  readability
* BREAKING CHANGE: Remove `AtRef(int)` and `AddPart(Message*)` member functions
* Add various const overloads
* Add `Empty()` and `Clear()` member functions
* Add `noexcept` where applicable
2022-05-28 15:14:25 +02:00
..
CMakeLists.txt ci: Run additional checks 2021-07-07 14:43:32 +02:00
ex-n-m-pair-topology.xml test: Increase log level 2021-07-07 14:43:32 +02:00
ex-n-m-topology.xml test: Increase log level 2021-07-07 14:43:32 +02:00
fairmq-ex-n-m-env.sh Add example and test of a n-to-m topology, incuding sub-channel use 2020-03-11 14:51:19 +01:00
fairmq-start-ex-n-m-dds.sh.in feat: Require DDS 3.5.13.7 2021-07-07 14:43:32 +02:00
fairmq-start-ex-n-m-pair-dds.sh.in feat: Require DDS 3.5.13.7 2021-07-07 14:43:32 +02:00
fairmq-start-ex-n-m-pair.sh.in Add example and test of a n-to-m topology, incuding sub-channel use 2020-03-11 14:51:19 +01:00
fairmq-start-ex-n-m.sh.in Add example and test of a n-to-m topology, incuding sub-channel use 2020-03-11 14:51:19 +01:00
Header.h Add example and test of a n-to-m topology, incuding sub-channel use 2020-03-11 14:51:19 +01:00
README.md Add example and test of a n-to-m topology, incuding sub-channel use 2020-03-11 14:51:19 +01:00
receiver.cxx feat(Parts)!: Refine and tweak 2022-05-28 15:14:25 +02:00
sender.cxx Don't use to-be-deprecated names 2022-01-24 06:40:24 +01:00
synchronizer.cxx Don't use to-be-deprecated names 2022-01-24 06:40:24 +01:00

README.md

N-M

A topology consisting of three layers of devices: synchronizer -> sender(s) -> receiver(s). Senders distribute data to receivers based on the data id contained in the message from the synchronizer (same id goes to the same receiver from every sender). The senders send the data in a non-blocking fashion - if queue is full or receiver is down, data is discarded. Two configurations are provided - one using push/pull channels between senders/receivers, another using pair channels. In push/pull case there is only one receiving channel on the receiver device. In pair case there are as many receiver (sub-)channels as there are senders.