Garrett D'Amore wrote:
> As far as extensible interface from sysmon to powerd, I rather like the
> idea of sending property lists, but I would prefer to use some kind of
> packed format.  I don't want to force the kernel to pack up XML just to

Why not just use property lists anyway? The code is there now and will
work, and if libprop ever grows a packed format (and benchmarking shows it
to even be worth the trouble to think about) then the interface from sysmon
to powerd becomes packed transparently, and nobody had to roll yet another
interface.

> Rather than go down the path of inventing a new format, why not just put
> this in XML.  The code lives in userland, so an XML parser isn't too big
> a deal.   Plus you get all the extensibility, etc.

When we talk about the format for the human-configured file, I lean in the
other direction. XML is a human-readable format in exactly the sense that
humans are capable of reading it when forced to, but there are things humans
shouldn't be forced to read. There'd be not much wrong with ant, if they had
defined some concise, readable make-like syntax (improving on the original
as much as they liked) and made the tool generate their XML goo from that.

-Chap