On 3 March 2016 at 01:34, Salz, Rich <rs...@akamai.com> wrote: > Are there common and well-specified semantics for merging "paged" JSON > objects?
For arrays, yes. It follows the pattern established with Atom, but it's fairly widely used. You put N things in the response, then provide a rel=next link for the next part. > Is his necessary? The serve can just stream it out and any client who is > asking for this huge name must be willing to generate it, too. Or is that > wrong? Consuming a huge blob of JSON is pretty unwieldy. JSON doesn't have a SAX-equivalent API, so you are reduced to sucking the whole object up into memory. There is RFC 7464, which cuts it back to something manageable, but it is also yet-another format. https://tools.ietf.org/html/rfc7464 _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
