IETF Logo Mail Archive

Re: [Json] JSON and int64s - any change in current best practice since I-JSON

Pete Cordell <petejson@codalogic.com> Wed, 17 January 2024 09:20 UTC

Return-Path: <petejson@codalogic.com>
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 6F2EBC151097 for <json@ietfa.amsl.com>; Wed, 17 Jan 2024 01:20:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=codalogic.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5O2Gn9j44nqx for <json@ietfa.amsl.com>; Wed, 17 Jan 2024 01:20:04 -0800 (PST)
Received: from sxb1nlsmtp03.prod.sxb1.secureserver.net (sxb1nlsmtp03.prod.sxb1.secureserver.net [92.204.71.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C4FC14F709 for <json@ietf.org>; Wed, 17 Jan 2024 01:20:03 -0800 (PST)
Received: from codalogic.com ([92.205.28.31]) by : HOSTING RELAY : with ESMTP id Q24br4ArVNbNCQ24brXHpy; Wed, 17 Jan 2024 02:19:01 -0700
X-SECURESERVER-ACCT: 92.205.28.31
x-originating-ip: 92.205.28.31
X-CMAE-Analysis: v=2.4 cv=MNjDm9Zl c=1 sm=1 tr=0 ts=65a79b85 a=JLy5cBbKnJYyhq39FObxXg==:117 a=JLy5cBbKnJYyhq39FObxXg==:17 a=IkcTkHD0fZMA:10 a=dEuoMetlWLkA:10 a=NEAV23lmAAAA:8 a=oLBq6S-zBa4Uxfi10EcA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codalogic.com; s=default; t=1705483141; bh=/5/A4iEJI0P581pCJLXq5/P2yceGx379TUUeQeAP+zw=; h=Received:Received:Subject:To:From; b=gMkqcUVbueNtdUe16k4dFd/mYmKi4yuxhEU79hL/sTOvDd/xifkwhfJzN0iUorm4x rL5T7vs7ZwAUwDXCxNo/tO3DjeOOrLFrivlEjWGbyYnITdzWrNp/+2RI/6zVBvOBPp OTxX3COnZDOISN2SggefdcziSG63TETcliSpUlWU=
Received: (qmail 25871 invoked from network); 17 Jan 2024 09:19:01 +0000
Authentication-Results: 31.28.205.92.host.secureserver.net; spf=pass (sender IP is 86.181.217.85) smtp.mailfrom=petejson@codalogic.com smtp.helo=[192.168.1.72]
Received-SPF: pass (31.28.205.92.host.secureserver.net: connection is authenticated)
Received: from host86-181-217-85.range86-181.btcentralplus.com (HELO ?192.168.1.72?) (86.181.217.85) by 31.28.205.92.host.secureserver.net with ESMTPSA (AES128-GCM-SHA256 encrypted, authenticated); 17 Jan 2024 09:19:01 +0000
Message-ID: <807fea1b-a22b-4d6b-aa5d-720c9b12023c@codalogic.com>
Date: Wed, 17 Jan 2024 09:19:00 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: Joe Hildebrand <hildjj@cursive.net>, "json@ietf.org" <json@ietf.org>
References: <87527a42-aaac-4f39-b320-05f18a2808c1@codalogic.com> <C31BF4C8-9E6C-48F8-BF7B-D2C379273B3F@tzi.org> <CAHBU6it4SaLawSiBgK9ySkbxjtHE6CX-P3r=hzcVy4ksoQo-Cg@mail.gmail.com> <CAChr6SxHfLW-A1asAndKJz-AiyJv5QP18bi=_bNdKXw7zYHThw@mail.gmail.com> <CAChr6SweYdCWxSABZ7g20Zd-xBFzcK0Ritq53S7WtjSwc-vLmw@mail.gmail.com> <E5A68370-CC2F-4618-AB39-39A382656616@cursive.net>
From: Pete Cordell <petejson@codalogic.com>
In-Reply-To: <E5A68370-CC2F-4618-AB39-39A382656616@cursive.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4xfO/zbx5ojmmrN+lKrfWM/lvqzot8hkJ/d7ERGuOGdwWPcRxx9AeZanoB2UQRu0VdEv+Md1ntSrmmUFPi6f/Qvwpiu+hajEgVKI7l46BQBVJUdtMvIClC /AofWfyWoqaAJOnEbCry2SzoDT7LF+sJkK3RkHzo7nn4iZLuSlPPqmd8VIDiUhAtOC5m+IyZIsooNg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/-ar-V8VX-gcf2QNd3QywHfdyzPk>
Subject: Re: [Json] JSON and int64s - any change in current best practice since I-JSON
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 17 Jan 2024 09:20:09 -0000

On 17/01/2024 04:49, Joe Hildebrand wrote:
> Another approach on the horizon is:
> 
> https://github.com/tc39/proposal-json-parse-with-source
> 
> Still, moving to CBOR is likely to get you much better interoperability, as mentioned in this thread.

Thanks, Joe.  That's very interesting.

It makes my wonder, does anyone know of any existing JavaScript 
libraries that a browser can download on the fly that can parse JSON 
with big numbers?

Thanks again,

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
---------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email