W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2013

Re: [whatwg] asynchronous JSON.parse

From: David Rajchenbach-Teller <dteller@mozilla.com>
Date: Fri, 08 Mar 2013 00:25:21 +0100
Message-ID: <513921E1.2000705@mozilla.com>
To: Dan Beam <dbeam@chromium.org>
Cc: WHATWG <whatwg@whatwg.org>
It is.

However, to use Transferable objects for purpose of implementing
asynchronous parse/stringify, one needs conversions of JSON objects
from/to Transferable objects. As it turns out, these conversions are
just variants on JSON parse/stringify, so we have not simplified the issue.

Note that I would be quite satisfied with an efficient, asynchronous,
implementation of these [de]serializations of JSON from/to Transferable
objects.

Best regards,
 David

On Thu Mar  7 23:37:43 2013, Dan Beam wrote:
> Isn't this precisely what Transferable objects are for?
> http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#transferable-objects

-- 
David Rajchenbach-Teller, PhD
 Performance Team, Mozilla
Received on Thursday, 7 March 2013 23:25:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 March 2013 23:25:48 GMT