2 =======================================
4 - Implement a factory method to create the Pingers objects. Something like:
5 smart_ptr<Pinger> pinger_ptr = PingerCreator::create(PingerCreator::Boost)
7 - Design a timer class on top of boost timer, but simpler.
9 - Include the i18n_noop in the strings, but this requires linking with the
12 - Use the I2n::Logger to log messages.
17 =======================================
19 - If one of the "[host]" in the configuration file omit the "interval" entry,
20 the application uses the next "[host]"'s "interval" entry, instead of a
21 default value. The problem is specific to the configuration read classes
22 that are not smart enough to verify which "[host]" have this entry and which
33 Thus, the tuples will be (A,1) , (B,3), (C,?), but A should have a default
34 value, instead of borrow B's value.
36 - The interval between each ping to the same host is 1 second later than in the
37 configuration file. For example, a ping configured to be performed each 5
40 - The overhead when handling a link that is down causes delays with the next
41 pings. This happens if the ping interval is a value close to the ping timeout.
42 So the application wait this amount to ping the next host.
43 This bug has something to do with the blocking ping, because the ping method
44 returns only after a reply or timeout, thus increasing the interval to the
45 next schedule ping to the same host and to the other hosts.