Difference: EcalODMonitoring (1 vs. 2)

Revision 22009-11-19 - AlessandroThea

Line: 1 to 1
 
META TOPICPARENT name="AlessandroThea"

Monitoring Framework

  • Disentangle the Client Class and the WebApplication Class. The trouble now is that the current implementation cannot bind methods of the Client to the WebApplication using the standard toolbox::taks::bind. A new implementation would be required. It becomes visible when trying to bind any ecal::mon::Client method for a workloop or similar stuff. As ecal::mon::Client doesn't inherits from Class, it has no addMethod method, required by the toolbox::task::bind. Possible patch: define a new method bind, between Client and WebApplication

  • If the previous point is solved, add the
Changed:
<
<
>
>
 

TriggerMonitor

  • Clean up the data structure and flow

Revision 12009-08-20 - AlessandroThea

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AlessandroThea"

Monitoring Framework

  • Disentangle the Client Class and the WebApplication Class. The trouble now is that the current implementation cannot bind methods of the Client to the WebApplication using the standard toolbox::taks::bind. A new implementation would be required. It becomes visible when trying to bind any ecal::mon::Client method for a workloop or similar stuff. As ecal::mon::Client doesn't inherits from Class, it has no addMethod method, required by the toolbox::task::bind. Possible patch: define a new method bind, between Client and WebApplication

  • If the previous point is solved, add the

TriggerMonitor

  • Clean up the data structure and flow

Alarming

-- AlessandroThea - 2009-08-20

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback