Changes to Trivial Implementation

* Changed to reflect that multi-line JSON does not need to be accepted.
* Added constraint that JSON parsing should only be done between (and including) outermost curly brackets found on each line.  This is a fix I needed to handle a client who was testing with a particular Windows Telnet client.

Question: Are all NDJSON lines assumed to contain JSON objects (which is all I use, or have seen in the wild), or could they be single JSON primitives (a number, string or bool) or Arrays?  In this case the curly bracket functionality won't work.

I think that using only JSON primitives can be ruled out as a use case, as that's a degenerate case, but newline separated Arrays or JSON might be a real use case.


I am not very happy with this complex definition of a line. Maybe we can just irgnore non-printable chars.