Mirror/FairMQ
1
0
Fork 0
mirror of https://github.com/FairRootGroup/FairMQ.git synced 2025-10-13 08:41:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
7ab6afa28a
FairMQ/examples/MQ/5-req-rep
History
Alexey Rybalchenko 7ab6afa28a Remove compile time transport interface switch 
- Remove the compile time check of the transport implementation.
  The transport (zeromq/nanomsg) can be chosen at run time with:
  `device.SetTransport("zeromq"); // possible values are "zeromq" and "nanomsg"`.

  For devices that use FairMQProgOptions, the transport can be configured via cmd option:
  `--transport zeromq` or `--transport nanomsg`. Default values is "zeromq".
  The device receives the configured value with:
  `device.SetTransport(config.GetValue<std::string>("transport"));`

  Old method of setting transport still works. But the NANOMSG constant is not defined.

- Remove old `fairmq/prototest` directory. It was only used as a test for protobuf.
  The protobuf part of Tutorial3 does the same (with different values).

- Fix a bug in FairMQPollerNN, where the `revents` value was not initialized.
  This caused the `poller->CheckOutput()` to trigger when it should not.
2018-05-02 16:12:57 +02:00
..
CMakeLists.txt Remove compile time transport interface switch 2018-05-02 16:12:57 +02:00
ex5-req-rep.json Update device configuration 2018-05-02 16:12:57 +02:00
FairMQExample5Client.cxx Rename /example to /examples and move MQ examples in it 2018-05-02 16:12:57 +02:00
FairMQExample5Client.h Rename /example to /examples and move MQ examples in it 2018-05-02 16:12:57 +02:00
FairMQExample5Server.cxx Rename /example to /examples and move MQ examples in it 2018-05-02 16:12:57 +02:00
FairMQExample5Server.h Rename /example to /examples and move MQ examples in it 2018-05-02 16:12:57 +02:00
README.md Rename /example to /examples and move MQ examples in it 2018-05-02 16:12:57 +02:00
runExample5Client.cxx Remove compile time transport interface switch 2018-05-02 16:12:57 +02:00
runExample5Server.cxx Remove compile time transport interface switch 2018-05-02 16:12:57 +02:00

README.md

Example 5: Request & Reply

This topology contains two devices that communicate with each other via the REQUEST-REPLY pettern. Bidirectional communication via a single socket.