[vwrap] #10: JSON serialization of binary values
"vwrap issue tracker" <trac@tools.ietf.org> Wed, 31 March 2010 21:45 UTC
Return-Path: <trac@tools.ietf.org>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id C7C953A6AAE for <vwrap@core3.amsl.com>;
Wed, 31 Mar 2010 14:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.935
X-Spam-Level:
X-Spam-Status: No, score=-100.935 tagged_above=-999 required=5 tests=[AWL=0.535,
BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001,
USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBrwRjDuRKlY for
<vwrap@core3.amsl.com>; Wed, 31 Mar 2010 14:45:01 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a])
by core3.amsl.com (Postfix) with ESMTP id 36F043A6A5E for <vwrap@ietf.org>;
Wed, 31 Mar 2010 14:45:01 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by
zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from
<trac@tools.ietf.org>) id 1Nx5jA-0004ze-3G; Wed, 31 Mar 2010 14:45:32 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "vwrap issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: markl@lindenlab.com
X-Trac-Project: vwrap
Date: Wed, 31 Mar 2010 21:45:32 -0000
X-URL: http://tools.ietf.org/vwrap/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/vwrap/trac/ticket/10
Message-ID: <059.6ea15d4d4ce293b70fa88f8379e0a5df@tools.ietf.org>
X-Trac-Ticket-ID: 10
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: markl@lindenlab.com, vwrap@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org);
SAEximRunCond expanded to false
X-Mailman-Approved-At: Wed, 31 Mar 2010 14:56:10 -0700
Cc: vwrap@ietf.org
Subject: [vwrap] #10: JSON serialization of binary values
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
List-Id: Virtual World Region Agent Protocol - IETF working group
<vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>,
<mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>,
<mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 21:45:01 -0000
#10: JSON serialization of binary values
--------------------------------+-------------------------------------------
Reporter: markl@… | Owner: markl@…
Type: defect | Status: new
Priority: major | Milestone:
Version: | Severity: -
Keywords: TypeSystem |
--------------------------------+-------------------------------------------
The JSON serialization of binary values is in the spec as an array of
integers. There was some discussion that this is undesirable, and that
serialization binary values as base64 encoded strings would be preferable.
JSON has no attributes, so this would act like a default conversion
between binary and string values, which currently isn't supported.
--
Ticket URL: <http://trac.tools.ietf.org/wg/vwrap/trac/ticket/10>
vwrap <http://tools.ietf.org/vwrap/>
- [vwrap] #10: JSON serialization of binary values vwrap issue tracker