On Wed, 3 Apr 2002, Henrik Nordstrom wrote:
> Not for Squid-2.. maybe if Squid-3 ever gets off the ground but
> XML is probably overly complex for this thing.. A Squid
> configuration does not have much of a hierarchy, and XML is best
> suited for hierarchically structured data.
XML is as flat or as hierarchical as you want it to be. The debate on
whether to use attributes (flat) or nested elements (hierarchical)
will never be closed.
One can, for example, convert all current squid.conf statements to a
list of
<option name="..." param1="..." ... />
elements so that the total effective depth remains the same. Not that
it is the smartest thing to do, but it is possible.
Among non-domain-specific languages, basic XML is ideal for
configuration without branching, variables, and other "dynamic"
concepts, IMO.
XML does not solve the #include problem as you will still need to
support that with internal (XML-based) or external preprocessor.
Alex.
Received on Wed Apr 03 2002 - 08:32:13 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:57 MST