On Tuesday 28 March 2006 23:52, Joe Desbonnet wrote:
Things like how to best
handle international characters.
A list of common pit falls.
Trying to create a "one size fits all" configuration language for all
Trying to shoehorn a popular data-encoding method (xml) into all niches you
can think of.
A a few
config file styles that are considered good, and a few that are
examples of how not to do it.
Good: Exim; dhcp; xinetd (as opposed to original inetd although the basic
ideas are similar, the directory structure allowing split files is a big
improvement over the single .conf file).
Bad: almost anything using .ini ;) *please note the ALMOST* if the data set
basically only has one or two dimensions, .ini will work fine. It will limit
you in the future, maybe.