On Sun, 15 Jul 2001, Peter Donald wrote:
> We could merge these into one file (config.xml) that has a format like
>
> <application>
> ...insert all of data from old server.xml here...
> <blocks>
> ...insert all of data from old config.xml here...
> </blocks>
> </application>
>
> The one objection to this was that the data underneat <blocks> is largely
> unstructured while the rest is structured.
>
> What is everyones opinions on this? Is it a good idea? Is it bad? What would
> you change? ;)
The question is what do we gain, if we aggregate these files into one?
Complexity isn't reduced, because all the info in these files still has to
be there. Personally I find that I almost never change server.xml, but
change config.xml quite frequently. I'd say if you were to get rid of all
of the many files involved in an Avalon installation (.xinfo, server.xml,
config.xml, assembly.xml), then that would be a definite cut down on
complexity. But I'm not sure if that is possible or even reasonable, the
files do have their purpose after all.
But unless someone can think of a compelling reason, I'd say to leave the
files as they are and save the users the work of updating their
installation.
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
