> > 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"...
What's wrong with the initial name, Watchdog? I think Watchdog very well describes what the classes are doing; they are watching some resource, waking up the configurator on changes. I think watchdog is the traditional name for classes like this. IMHO, scout would better describe a class that tries to locate something, looks for something. Another thing. I'm not sure if had already been brought up, but it would be nice if it was possible to attach a Configurator to the Watchdog in the properties-file. The Watchdog would have setConfigurator-method instead of the abstract reconfigure()-method. - Heikki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
