It would be helpful for FragmentGenerators to have access to Requests
Currently, the data requests that are received by BoardReaders are handled by core BR code (in CommandableFragmentGenerator).
Folks on protoDUNE/DUNE have requested that FragmentGenerators have access to data requests. This would be helpful in cases in which it is not practical to return all of the data that is received from the hardware in getNext_() calls. (For example, in the protoDUNE FELIX FragmentGenerator, there isn't enough CPU power to compress all of the data coming from the FELIX card, so the FragGen only compresses the data of interest. Currently there is a back-door way to get those windows of interest to the FragGen, and it would be nice to switch to a way of doing that which is more officially sanctioned/supported.)
Several of us have discussed this a bit. Eric suggested a protected method in CFG that returns a copy of the pending requests. In talking with Roland and Phil at protoDUNE, they requested that we have two methods, one which returns the full list of pending requests (and may contain duplicates between calls) and one which returns a single "next" request (and would not return duplicates). Something like getRequests() and getNextRequest().