configuring producing service
mu2e is designing a conditions database producing service, based on art team
advice on being consistent with mulithreaded art. We would very much like
the regular modules to be able to communicate what conditions they need to
the conditions producing service at startup. We imagine a call like "consumes"
now does for art products. We are interested in any other ideas to achieve
the same ends. We do not favor configuring the service and the modules
in two coordinated parts of fcl as too error-prone for the naive user.
As part of the answer we were wondering if a producing service can
access a legacy global service, and how that ordering between them works.
#2 Updated by Kyle Knoepfel about 2 years ago
- Status changed from Under Discussion to Closed
This issue was discussed at a dedicated meeting. For the particular use case in question, it was decided to move away from using a service. This issue will be closed since it no longer applies. If the functionality described above needs to be considered again, a new issue will be created.