Variables | |
| and must be present Because it has no parameters to | configure |
| and must be present Because it has no parameters to and because it is always | created |
| analysis jobs want it to be The Plan To we should place the defaults into one structure which I will call MessageLoggerDefaults Its ctor should take as an argument an enum MessageLoggingMode::To there should be an option to cmsRun of mode which takes values etc One of we check the mode and send a message to the scribe indicating that it will need to construct its defaults accordingly To we note that the only serious headaches from these defaults would be the issue of different sets of and potential inability to remove or modify one of the defaulted values The latter concern is not really problematic because any configuration settings that do appear will everride the defautls we are supplying The destination list issue should be resolved as then that list will be REPLACED by the one actually supplied Steps A Use of the MessageLoggerDefaults decide what is in the structure We should make this nested probably A2 Create the modes which must live in MessageLogger rather than MessageService A3 Write a ctor based on the existing cfi for the basic default mode A4 Modify to use these defaults Pay attention to the issue of empty or non empty destination list A5 Unit test make certain the behavior with and without the cfi file is identical This unit test can be written in parallel to A1 and ought to send various sorts of messages so as to exercise the various settings B Supply of mode B1 Create a MODE opcode for the which causes the modes enum saved for use by configure |
Definition at line 1 of file CONFIGURATION_NOTES.txt.
| and must be present Because it has no parameters to and because it is always created |
Definition at line 1 of file CONFIGURATION_NOTES.txt.
1.8.11
