IETF Logo Mail Archive

Re: [Json] Using a non-whitespace separator (Re: Working Group Last Call on draft-ietf-json-text-sequence)

Nico Williams <nico@cryptonector.com> Thu, 05 June 2014 23:40 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A461A035B for <json@ietfa.amsl.com>; Thu, 5 Jun 2014 16:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXCjzrJjIL55 for <json@ietfa.amsl.com>; Thu, 5 Jun 2014 16:40:23 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D19CF1A0358 for <json@ietf.org>; Thu, 5 Jun 2014 16:40:23 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 8290554058 for <json@ietf.org>; Thu, 5 Jun 2014 16:40:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=tx4p+CK/4mAD6DHNPKG4 B8o4O6s=; b=oCBk9ygXyHsUbNGl5JkwD/R15artf7qiLcSojtQnKEBhUhi76zht RmcuYP2nnIXTSexwZQxXD+FHv53lUfGa/98QL0LklAexRyJlP/IM12ciisMNaqgq L/E9p3NHomnCD6XWaaFhNzjcZOyBv6Y3wR8I5ShmnDAYK61zkwCxYyU=
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 32A4854057 for <json@ietf.org>; Thu, 5 Jun 2014 16:40:17 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id bs8so29066wib.0 for <json@ietf.org>; Thu, 05 Jun 2014 16:40:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.12.135 with SMTP id y7mr2485022wib.39.1402011614953; Thu, 05 Jun 2014 16:40:14 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Thu, 5 Jun 2014 16:40:14 -0700 (PDT)
In-Reply-To: <20140605231607.GE15558@mercury.ccil.org>
References: <CAK3OfOja-17V391tTK91R98X8XQzd0iPnur2=oo4ii+MCOt+Rg@mail.gmail.com> <CFB42410.4EDDC%jhildebr@cisco.com> <CAMm+Lwime-=UQPu3t2ty05CZLb7xUMi9KGi31Xi2B7RNF5S3Og@mail.gmail.com> <CAK3OfOg_k4Ngq+z1pn4b+XRf0M1Hqx8qZ9BtW0sa8QQ+bjKJyA@mail.gmail.com> <084664DB-A55D-465E-8888-97BA0BB59637@vpnc.org> <CAHBU6itEph5GzB-P8bUUvUMopRNxcCE-16qys7ofhdmsDvpN4w@mail.gmail.com> <CAMm+LwjoeC1R4O2iCPo+RfUFn4Qca4zyytqa817ayH60mNaWLg@mail.gmail.com> <CAK3OfOhjPZUXK6C0qSsQQZvOgR3Sv3SWpyH=qTuihuDC9uvXrA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11546B21D22@WSMSG3153V.srv.dir.telstra.com> <93018E84-581D-4B75-8B58-6BFAD27D8EE3@vpnc.org> <20140605231607.GE15558@mercury.ccil.org>
Date: Thu, 05 Jun 2014 18:40:14 -0500
Message-ID: <CAK3OfOj6NQJcyNLZbsZ1vyXOD4dQSgPj+V-6smN_HQazw1=b=Q@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/zHy2_-jEpglg6H7I1AbZ18PN-60
Cc: "Manger, James" <James.H.Manger@team.telstra.com>, Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Using a non-whitespace separator (Re: Working Group Last Call on draft-ietf-json-text-sequence)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 05 Jun 2014 23:40:24 -0000

On Thu, Jun 5, 2014 at 6:16 PM, John Cowan <cowan@mercury.ccil.org> wrote:
> Paul Hoffman scripsit:
>> As a summary from below: you prefer a more normal character like NL
>> plus the need to escape it in strings, versus an obscure character
>> like RS that requires no escaping. Is that correct?
>
> Both require escaping in strings.  The difference is that LF can appear as
> insignificant whitespace, whereas RS cannot.  So to achieve the same thing
> as RS achieves (restartable/correctable writes), it's simply necessary never
> to spit out an insignificant LF.

Or to remove any LFs.  Since unescaped LFs are insignificant in JSON
texts, it's always OK to remove them without parsing and re-encoding.

Your argument is convincing to me: there's no real difference between
RS and LF this way.

Perhaps someone can explain why it would be bad for log writers to
remove [unescaped] LFs from JSON texts?  I can't tell why it's bad.  I
only know that some object.

Nico
--

v2.29.0 | Report a Bug | By Email | System Status