Re: One True Way (TM) of handling configuration files

[Craig Wohlfeil]

I think this is a good idea. One thing that sys admin people that I work 
with like about WebSphere 4 is the centralized config repository that 
can be managed from any machine in the cluster. There is no need for a 
special admin server. This could make clustering easier. No need to 
replicate configuration. What happens if the config server is down?

Ideally, the server should just be able to start w/o any forms of 
configuration, and then for the rest of the configuration to be managed 
dynamically. My preference, esp. for distributed clusters, would be to 
use some kind of central repository config that elements interacted 
with, and for that to be backed by some kind of DB. That way, the DB can 
be replicated across multiple machines, edited synchronously and minor 
changes won't need huge restarts.