2011/2/17 Grégory Starck <g.sta...@gmail.com>
> [...]
>
> well, finally I got the whole thing ok (test_livestatus included) : (but)
> for this I had "simply" to use a copy.deepcopy at livestatus level .. but
> now with this fix I have all features ok with Thruk for comments &
> downtimes ; and the tests normally still are ok too :)
>
> don't know if this would be acceptable to you ?? because now for
> manage_brok we'll have a copy of the brok every time be done.. not sure
> it's acceptable from a performance point of view, wdty ?
>
Is the copy in the module code or in the test_livestatus one? If it's just
in the test it's not a problem, but it can be if it's in the module. If it
is in the module code, just put a deepcopy in update_brok in test_livestatus
code, so even Downtime nested in the dict will be duplicated without
problem.
Jean
>
> greg.
>
>
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
