In the model where the Request messages also serve to provide Routing information, "push mode" BoardReaders will need to have a RequestReceiver configured, but it should be on a separate channel from the Requests coming from EventBuilders. These "push mode" requests would replace routing tables. (Note that the Request protocol already allows multiple requests to be sent in a single multicast datagram).
This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/22534 (FNAL account required) Originally created by @eflumerf on 2019-05-08 02:23:55
In the model where the Request messages also serve to provide Routing information, "push mode" BoardReaders will need to have a RequestReceiver configured, but it should be on a separate channel from the Requests coming from EventBuilders. These "push mode" requests would replace routing tables. (Note that the Request protocol already allows multiple requests to be sent in a single multicast datagram).