Prevents direct modification of the xDAQ application InfoSpace
Summary
At the moment, the xDAQ application configuration InfoSpace can be directly modified by any application through a SOAP call. This should be prevented since no check is performed on the variables, the InfoSpace is not thread-safe, and values should be changed at any time.
What is the expected correct behavior?
The InfoSpace is not modified on-the-fly by random applications but used only as a static configuration set through the application XML configuration.
Dynamic variables can be set through specific update SOAP calls or during the state transition calls thanks to additional parameters.
Possible fixes
The TCDS control applications use the xDAQ event in a very sane way and prevent any modification of the application InfoSpace through the re-definition of the ParameterSet
SOAP call: https://gitlab.cern.ch/cmsos/tcds/-/blob/16ca31e50d3d75db7ba50b161dae4dc72605cf6d/tcds/utils/src/common/XDAQAppBase.cc#L91
Note that the fix is not trivial since some GEM applications rely on their InfoSpace to be modified on-the-fly.