Anton Aylward wrote:
On 12/20/2016 02:55 AM, Per Jessen wrote:
Anton Aylward wrote:
In the mean time, the real issue isn't that you can't import a snapshot of the journalctl into oocalc, its that ooclc ignores the JSON standard unless you have the add-in for it. Seems dumb to me that it should handle CSV and not JSON in this day and age.
For largish amounts of data (megabytes), JSON or XML is overkill, but CSV is very efficient.
if you're talking "byte efficient" as in low overhead, then yes.
Not only that, but compression works very well, so transmission time and storage footprint are less important. I was more thinking of subsequent processing, loading into databases and such.
But the whole point of something like XML is not about byte efficiency, it is about semantic clarity and error handling. A few garbled bytes of a CSV writes off everything that follows. A few garbled bytes of a XML transmission resyncs on the following stanza because of the semantic structure.
Anton, you're not actually trying to argue that you would use XML to ensure proper data transmission? :-) XML and JSON both have their places, but when I'm downloading 1million lines of log entries and "cooking" them down to 125.000 new database entries, they're both out place, IMHO. (and that's the logdata from just one mirror site). Massaging that data in and out of XML or JSON format would be 100% overhead.
JSON is similar though the contrast between XML and JSON is rather like between ALGOL and C with respect to keywords vs curly brackets.
They're both just structured formats for data interchange - you could also mention EDI or the PHP serialize format. When sender and recipient cannot or will not agree on a common format, using XML or JSON can solve the problem.
Yes, I'm perfectly aware that you cold code up a packetized protocol for CSV with checksum for each packet and acknowledgement of good receipt vs request of retransmission, sort of like TCP writ large.
Right, that's called TCP. Or maybe rsync over TCP.
But pretty soon you get into the overhead and you get into all the issues with queueing and flow control that has produced hundreds of studies and papers about TCP packet management over the decades. You really don't want to go there.
Use XML or JSON instead.
Not for volume data transmission between two cooperating parties. It's only 100% overhead. -- Per Jessen, Zürich (1.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org