W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Exposing structured clone as an API?

From: Brendan Eich <brendan@secure.meer.net>
Date: Fri, 24 Apr 2015 15:41:27 -0700
Message-ID: <553AC697.90303@secure.meer.net>
To: Anne van Kesteren <annevk@annevk.nl>
CC: Joshua Bell <jsbell@google.com>, Robin Berjon <robin@w3.org>, Ted Mielczarek <ted@mozilla.com>, public-webapps <public-webapps@w3.org>, Katelyn Gadd <kg@luminance.org>
Step where you need to, to avoid falling over :-P.

The problems with generalized/extensible clone are clear but we have 
structured clone already. It is based on a hardcoded type-case 
statement. It could be improved a bit without trying to solve all 
possible problems, IMHO.

/be

Anne van Kesteren wrote:
> On Fri, Apr 24, 2015 at 3:13 PM, Joshua Bell<jsbell@google.com>  wrote:
>> >  If we're not dragging in the notion of extensibility, is there complication?
>
> I would be fine with adding an API without extensibility. I was just
> afraid we might step on TC39's toes, but maybe since they're not
> helping out with structured clones that's okay?
Received on Friday, 24 April 2015 22:41:58 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC