[MUD-Dev] Re: Why modules? (Was: Inheritable modules)
Vadim Tkachenko
vt at freehold.crocodile.org
Mon Nov 2 22:27:59 CET 1998
Jon A. Lambert wrote:
>
> On 2 Nov 98, Vadim Tkachenko wrote:
> > Jon A. Lambert wrote:
> >
> > [I'll be dropping little remarks here and there today...]
> >
> > > I also view configuration information as a candidate for runtime
> > > dynamism. Another source of unnecessary rebooting.
> >
> > Think about this (in Java SYNTAX, not semantics):
> >
> > class Configuration extends EventMulticaster;
> > interface ConfigurationChangeListener;
> >
> > Rings a bell?
>
> Yes. Ding.
> This says a lot in a little. A solution dynamic configuration
> problem using a variation of the Observer pattern.
> This works for me. Now make Configuration persistent.
OK.
class ConfigReader extends LineNumberReader;
class PropertiesReader extends ConfigReader;
class ConfigurationRepository extends Hashtable; /* actually, this is
irrelevant to two lines above, but important in terms of different
configuration sets for different modules */
Rings a bell? ;-)
> --/*\ Jon A. Lambert - TychoMUD Internet:jlsysinc at ix.netcom.com /*\--
--
Still alive and smile stays on,
Vadim Tkachenko <vt at freehold.crocodile.org>
--
UNIX _is_ user friendly, he's just very picky about who his friends are
More information about the mud-dev-archive
mailing list