Re: If not JSON, what then ?
Kari hurtta <hurtta-ietf@elmme-mailer.org> Wed, 03 August 2016 09:45 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B59E612D8F5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 3 Aug 2016 02:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.208
X-Spam-Level:
X-Spam-Status: No, score=-8.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 5hC48-zBphI9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 3 Aug 2016 02:45:39 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 280C812D100 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 3 Aug 2016 02:45:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bUsg1-0007JT-BZ for ietf-http-wg-dist@listhub.w3.org; Wed, 03 Aug 2016 09:41:25 +0000
Resent-Date: Wed, 03 Aug 2016 09:41:25 +0000
Resent-Message-Id: <E1bUsg1-0007JT-BZ@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <hurtta@siilo.fmi.fi>) id 1bUsfx-0007Hy-Np for ietf-http-wg@listhub.w3.org; Wed, 03 Aug 2016 09:41:21 +0000
Received: from smtpvgate.fmi.fi ([193.166.223.36]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <hurtta@siilo.fmi.fi>) id 1bUsfc-000897-Mj for ietf-http-wg@w3.org; Wed, 03 Aug 2016 09:41:20 +0000
Received: from virkku.fmi.fi (virkku.fmi.fi [193.166.211.54]) (envelope-from hurtta@siilo.fmi.fi) by smtpVgate.fmi.fi (8.13.8/8.13.8/smtpgate-20160114/smtpVgate) with ESMTP id u739bpfN018790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Aug 2016 12:37:52 +0300
Received: from shell.siilo.fmi.fi by virkku.fmi.fi with ESMTP id u739bpnB000872 ; Wed, 3 Aug 2016 12:37:51 +0300
Received: from shell.siilo.fmi.fi ([127.0.0.1]) by shell.siilo.fmi.fi with ESMTP id u739bpIS007543 ; Wed, 3 Aug 2016 12:37:51 +0300
Received: by shell.siilo.fmi.fi id u739bpxx007542; Wed, 3 Aug 2016 12:37:51 +0300
Message-Id: <201608030937.u739bpxx007542@shell.siilo.fmi.fi>
In-Reply-To: <20160803064633.GB500@1wt.eu>
References: <12ED69B4-C924-475E-9432-B8FEB4B9DF80@mnot.net> <20160803063730.EDABAF792@welho-filter3.welho.com> <20160803064633.GB500@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
Date: Wed, 03 Aug 2016 12:37:51 +0300
Sender: hurtta@siilo.fmi.fi
From: Kari hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari hurtta <hurtta-ietf@elmme-mailer.org>, HTTP working group mailing list <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>, Poul-Henning Kamp <phk@phk.freebsd.dk>
X-Mailer: ELM [version ME+ 2.5 PLalpha41]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="US-ASCII"
X-Filter: smtpVgate.fmi.fi: 3 received headers rewritten with id 20160803/24457/01
X-Filter: smtpVgate.fmi.fi: ID 24457/01, 1 parts scanned for known viruses
X-Filter: virkku.fmi.fi: ID 11726/01, 1 parts scanned for known viruses
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (smtpVgate.fmi.fi [193.166.223.36]); Wed, 03 Aug 2016 12:37:52 +0300 (EEST)
Received-SPF: none client-ip=193.166.223.36; envelope-from=hurtta@siilo.fmi.fi; helo=smtpVgate.fmi.fi
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: AWL=-1.827, BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.245, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bUsfc-000897-Mj cf2c039e8d4a9db4455c5e9a063aee82
X-Original-To: ietf-http-wg@w3.org
Subject: Re: If not JSON, what then ?
Archived-At: <http://www.w3.org/mid/201608030937.u739bpxx007542@shell.siilo.fmi.fi>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32164
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Willy Tarreau <w@1wt.eu>: (Wed Aug 3 09:46:33 2016) > On Wed, Aug 03, 2016 at 09:37:30AM +0300, Kari hurtta wrote: > > | 2) Regardless of #1, using < as your indicator character is going to collide with the existing syntax of the > > | Link header. > > > > Or perhaps use ':' as indicator? Causes double '::' on HTTP/1 > > > > Date::1470205476 > > > > Is this viable ? > > It could but strictly speaking it will not be "::", it would just be ":" > to start the value, because your field above parses as ":1470205476" for > the value and will be rewritten like this along the path by many > implementations : > > Date: :1470205476 Yes, that is true. Another possibility is use indicator from ascii control block. For example byte 01. Does not collide with existing use. That is Date:1470205476 on HTTP/1 (but probaly not visible; first character after ':' is byte 01 (ctrl-A)). ( I think that someone suggested that already. ) ( byte 01 seems to be valid TEXT on ABNF ? ) > Willy / Kari Hurtta
- Re: If not JSON, what then ? Sam Johnston
- Re: If not JSON, what then ? Martin J. Dürst
- Re: If not JSON, what then ? Alcides Viamontes E
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Martin Thomson
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Martin Thomson
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Kari hurtta
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Kari hurtta
- Re: If not JSON, what then ? Martin Thomson
- Re: If not JSON, what then ? Carsten Bormann
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? Carsten Bormann
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Carsten Bormann
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Stefan Eissing
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? nicolas.mailhot
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? nicolas.mailhot
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Stefan Eissing
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Mark Nottingham
- Re: If not JSON, what then ? James M Snell
- Re: If not JSON, what then ? Cory Benfield
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Nicolas Mailhot
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Poul-Henning Kamp
- Re: If not JSON, what then ? Willy Tarreau
- Re: If not JSON, what then ? Carsten Bormann
- If not JSON, what then ? Poul-Henning Kamp