all right :

(better_interface)greg@brutus:~/Documents/Projets/shinken$ git diff --stat master 
 shinken/                    |   82 ++++++-
 shinken/daemons/     |  106 ++-------
 shinken/daemons/      |  399 ++++++++++++---------------------
 shinken/daemons/      |    2 +-
 shinken/daemons/ |    2 +-
 shinken/daemons/   |  242 +++++++--------------
 shinken/                 |  360 ++++++++++++-------------------
 shinken/                 |    2 +-
 test/                 |    2 +-
 test/               |    2 +-
 10 files changed, 459 insertions(+), 740 deletions(-)

as usual with changes on the core daemon codes I hope this won't break too much by everyone..

basically what's in this factorization:  

- again some Daemon code factorized (like "wait_for_initial_conf") (and now with that I think Daemon is nearly as "good" as it can be (modulo the fact that some methods should really be transformed to private methods because there are quite a lot in Daemon).

- but also and more importantly :  factorized the "pyro objects" interface  (IForArbiters, IBroks, etc....).

I'm finishing some further manual tests (actually end_to_end + quick_tests are already good) on this and then I will push that normally later today..

it's more than possible that some last clean or simplification or correction will be needed there and there after that..   eventually also for some attribute rename but not that much.

By the way, still on this matter of code factorization :  I see that the modules management code (when a daemon receives its modules in a (new) conf from arbiter(or scheduler)) is not very "good" (imho) :  nearly every daemon manages that in a different way (and not necessarily 100% robust) ;  I think that it is also possible to factorize/handle that quite better..  but that won't be for these days ;)

just to check : Jean do you see what I mean here ??  will it be good to factorize/clean that also ?