Separate Request Buffering from Request Receiving
In the current artdaq model, RequestReceiver is instantiated by CommandableFragmentGenerator and is responsible for receiving request as well as storing them and making them available to CFG upon request. In a more modular view of artdaq, the request receiving capability should be separated from the request storage, so that RequestReceiver could be replaced with a different implementation and not affect the CFG code.
#1 Updated by Eric Flumerfelt 7 months ago
- Status changed from New to Resolved
This has been implemented on artdaq:feature/24398_RequestReceiver_RequestBufferSeparation. There is a configuration change on artdaq-utilities-daqinterface:feature/24398_RequestReceiver_CfgChanges; all BoardReaders in pull mode need to set "receive_requests: true", similar to how EventBuilders must set "send_requests: true" if they intend to send requests.