Re: [Json] The names within an object SHOULD be unique.

John Cowan <cowan@mercury.ccil.org> Tue, 30 July 2013 14:26 UTC

Return-Path: <cowan@ccil.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8115821E80E8 for <json@ietfa.amsl.com>; Tue, 30 Jul 2013 07:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2tNaYIrrLmb for <json@ietfa.amsl.com>; Tue, 30 Jul 2013 07:26:51 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 86D0411E80D3 for <json@ietf.org>; Tue, 30 Jul 2013 07:26:25 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1V4AsZ-0004TR-KH; Tue, 30 Jul 2013 10:26:23 -0400
Date: Tue, 30 Jul 2013 10:26:23 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Message-ID: <20130730142623.GB17809@mercury.ccil.org>
References: <B4EBDF80-ED3C-4BAA-9441-AC1B46ED5D6A@jorgechamorro.com> <A723FC6ECC552A4D8C8249D9E07425A71416EFE8@xmb-rcd-x10.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71416EFE8@xmb-rcd-x10.cisco.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Jorge Chamorro <jorge@jorgechamorro.com>, "json@ietf.org WG" <json@ietf.org>
Subject: Re: [Json] The names within an object SHOULD be unique.
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 14:26:58 -0000

Joe Hildebrand (jhildebr) scripsit:

> I've never seen an implementation that is both streaming and
> not streaming at the same time.  Can you say more about how you'd
> write the API for that?  Better, can you give an example of such an
> implementation?

I haven't either, but I could see the uses of an implementation that
streamed arrays but not objects (of course, it could hardly stream an
array that was within an object).

> If you mean an application that takes a stream of complete JSON
> objects without wrapping them in an array, that problem is likely out
> of scope, and the processor would act identically to a non-streaming
> implementation in our existing worldview.

+1.  I was trying to think how to say that ....

-- 
John Cowan   cowan@ccil.org    http://ccil.org/~cowan
If a soldier is asked why he kills people who have done him no harm, or a
terrorist why he kills innocent people with his bombs, they can always
reply that war has been declared, and there are no innocent people in an
enemy country in wartime.  The answer is psychotic, but it is the answer
that humanity has given to every act of aggression in history.  --Northrop Frye