Harmeet,
These are the interfaces in question. > - How is WatchdogTarget associated with Watchdog ? The association is not > apparent. The WatchdogTarget is the target for the Watchdog upon the triggering event. I don't see how could find this unclear. It's certainly at least as clear as the relationship between Scheduler and Target. > - From the interface it appears there is a one to one mapping between a > watched object and watchdog. This seems to impose an additional thread per > watched object. Could this lead to scalability issues. For instance if > there > are 100 threads that can be associated with a Handler, can there now be at > most 50 concurrent handlers ? There is a one to one mapping between watched object and watch dog. That does not imply a thread limit in generic implementations, for all the reasons that Noel discussed earlier. There is such a one to one mapping in my Watchdog implementation. By design. As I've explained. Repeatedly. > - Is WatchDogTarget really needed ? Can Runnable act as WatchDog target ? Runnable has a specific semantic meaning. Runnable means that the class implementing the Runnable interface can be executed as the body of a thread. That's not necessarily true for a WatchdogTarget (in fact, it isn't for any of the code I posted). So no, you can't use Runnable. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
