> Secheduler has this method to associate a target.
> void addTrigger( String id, TimeTrigger trigger, Target target );
> Watchdog does not seem to have any callback association.
Please see my earlier response to you. I've already answered this subject
in detail.
> void addTarget(WatchdogTarget targ) ;
No. For reasons previously explained in this thread, and also because ADD
is a semantic that may not be appropriate. In some cases, SET is the
appropriate semantic. Please see MutatableWatchdog for that method.
> void startWatchdog(); to void startWatchdog(WatchdogTarget targ);
No. You are exposing the ability to set a target with the ability to start
a watchdog. That mixes two different interface notions.
> If via watchdog mechanism one thread can be associated with n watched
> objects, how would each watched object be identified at trigger time
> by the thread.
Asked and answered in a prior e-mail by me.
> Would it be better to have a generic Command interface.
Orthogonal issue. I've already written and submitted the latter (see the
archives), but there is no need to rewrite the entire protocol handler
mechanism at this time.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
