At 20:31 30.05.2002 -0700, [EMAIL PROTECTED] wrote: >Ceki, > >Thanks for your comments, my comments are below. > > > How about "Scout" or "ScriptScout"? A ScriptScout scouts for changes > > in configuration scripts. Scout is both a noun and a verb, so method > > names like startScouting or stopScouting make sense. > > > > I propose ScriptScout as the interface name and ScriptScoutBase as the > > base class implemented by FileScout, HTTPScout, SocketScout > > subclasses. > >Hmm. Well it does make sense. How about ConfigScout, etc? I don't know if >I want to use the word "script"...
Script is shorter than "Configuration File". I use the former as a synonym for the latter, especially in cases where length matters. ConfigScout is obviously fine too. > > Just remove the "watchdogThread.interrupt();" statement and your code > > will continue to run just as well. > >I will look at the references you have included. I guess I am a little >concerned about sleeping threads not being woken up to exit the >reconfigurator sooner. I see. A sleeping thread does not consume any CPU resources. By setting the variable "running" cleaner to false, you cause the watchdogThread to exit peacefully. The thread will hold to some memory while sleeping but that is hardly matter for concern. By setting the watchdogThread as a daemon thread, you have taken care of delays when exiting the application. One the other hand by calling watchdogThread.interrupt you must worry about catching/reacting to InterruptedExceptions and there is no way to know where or when these will be thrown. This particular case might be tractable but why take any risks with no gain to show for it? >-Mark -- Ceki SUICIDE BOMBING - A CRIME AGAINST HUMANITY Sign the petition: http://www.petitiononline.com/1234567b I am signatory number 22106. What is your number? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
