Re: [Json] serializing sequences of JSON values

[Nico Williams <[e-mail]>]

On Thu, Mar 13, 2014 at 11:04 PM, Tatu Saloranta <[e-mail]> wrote:
> Major challenge with sequence of XML documents is really just implementors,
> and inertia.
> Having written a fully conformat XML parser that optionally supports
> "fragment mode" (Woodstox for Java; implements SAX and Stax APIs) I can say
> that compared to all other work, supporting multiple root-level documents is
> a minor addition. Mode is used/useful for supporting XMPP, as well as for
> use for streaming logging, similar to what has been discussed for JSON. It
> has to be explicitly enabled (since such usage is non-compliant, having
> multiple roots).
>
> There are some minor details (like xml declaration, what to do if it is
> repeated) to deal with,
> to allow simple concatenation, but all in all it is not a big technical
> problem. I mean, compared to writing actual fully compliant parser
> (supporting DTD is 80+% of the deal).

By comparison, parsing a JSON text sequence can be done with any JSON
parser, especially when the encoder is nice enough to use "compact"
encoding options and uses newline as the separator.  To be efficient
it's best to have an incremental parser (that is, that can be fed
chunks of input until the end of the text is found).

That's how jq handles JSON text sequences.  It's really quite simple.

Nico
--