[email protected] wrote: > On Thu, 24 Jun 2010, Michael Biebl wrote: > >> Looking at the XML config example I have to admit that I don't >> really like how it looks and feels. >> >> Even david's example looks rather verbose and I also share the >> concern that such an XML file would be hard to edit using e.g. vi. >> >> I just stumbled upon >> http://stackoverflow.com/questions/1925305/best-config-file-format. >> >> >> One alternative already discussed here, is YAML. Then the site >> above mentions INI style format, which basically everyone knows but >> question is, if it's flexible enough. > > INI is good for one level of item->subvalue data, but with rsyslog I > think we need the ability to go arbararily deep > >> Has anyone experience with JSON or LUA? > > both of these are really full languages (or subsets of languages). I > don't think they are appropriate for config files (and I really > question them as being appropriate for data transfers, even though > JSON is used for this purpose extensivly)
Hmmm. It struck me a few-dozen posts back in this thread that the configfile language perhaps *needs* to be a full language. Many perl and PHP apps have config files that are really data declarations in perl or PHP; I thought of suggesting a configfile written in perl. Then I reconsidered. Could you elaborate your objection to using JSON? you say you "question" it, but we haven't seen your question. -- Jack. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
