Re: [Json] Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Patrik Fältström scripsit:

> This implies the whole thing is a UTF-8 encoded text that is to be
> parsed like this:

No, this is a misunderstanding.  There is no requirement that the sequence
*as a whole* is well-formed UTF-8 text.  For example, if the first JSON
text is written only in part for whatever reason (system crash, etc.) to
a log file, the next process can write a 0x1E byte and carry on.

> I.e. the blob, to be compliant with this document, MUST be UTF-8 encoded JSON.

The possible-JSON part is either UTF-8 encoded JSON or it's arbitrary junk.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@xxxxxxxx
Said Agatha Christie / To E. Philips Oppenheim
"Who is this Hemingway? / Who is this Proust?
Who is this Vladimir / Whatchamacallum,
This neopostrealist / Rabble?" she groused.
        --George Starbuck, Pith and Vinegar





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]