The Journal - a proposed syslog replacement
Posted Nov 20, 2011 7:55 UTC (Sun) by skissane
In reply to: The Journal - a proposed syslog replacement
Parent article: The Journal - a proposed syslog replacement
I think, if you want to stick to text, it would be much better if tools output in some standardised text format, e.g. XML, JSON, YAML, etc.
But then, once you have a standardised text format, why not save some space and processing time with an efficient binary serialization of XML/JSON/YAML/what-have-you?
And then you can have a tool, e.g. bin2text, which reads the binary format
on standard input and writes the text format on standard output, and vice
versa. With such a tool, reverse-engineering/examination should be no harder than with a plain text format.
I think this would be better than both (1) the rather poorly-defined text formats used at present by many tools and (2) binary is more efficient than text.
The point you make about trying to recover from corrupted files being easier when they are in text is true, but how often do you have to deal with that? If there were provided some good quality libraries (say C with bindings to other common languages such as C++, Java, Perl, Python, etc.), the odds of a corrupt file due to programmer error should be low, outside of some mid-transaction failure scenario. And if we had transaction support in the library or the underlying filesystem, we could avoid that problem too.
to post comments)