On Mon, Jun 21, 2010 at 9:09 AM, Rainer Gerhards <[email protected]> wrote: > > I think you mean this: > > <input name=inp10515 type=imtcp> > <params> > <param id="listen">10514</param> > <param id="ruleset">remote10514</param> > </params> > </input> > > But what's the advantage of this over > > <input name=inp10515 type=imtcp> > <params > listen="10514" > ruleset="remote10514" > /> > </input> > > I have to admit that I do not see an advantage, just more text to be written > (and IMHO harder to read due to more noise). So I personally prefer the > paramter approach. Also I don't see why it should become less readable if > there are many parameters. Isn't that just a matter of how you format the > source text? > > Maybe I am overlooking something obvious. I don't have much experience with > XML...
I also have nearly zero experience with XML - but the one-parameter-per-node approach "looks" cleaner to me. Either way though, XML is a fairly common thing - there has to be a best practices approach. If going the XML route (which I also have to admit makes a fair bit of sense), we should do everything to stick to standards and best practices. I know that this will make it significantly easier to write configuration frontends. -Aaron _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
