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

Re: Exposing structured clone as an API?

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 27 Apr 2015 11:54:11 +0200
Message-ID: <CADnb78hDOGu-wH=8ebgSaFWv+n=hCqKXoQnUC-dZYb5-=8qWdg@mail.gmail.com>
To: Brendan Eich <brendan@secure.meer.net>
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>
On Sat, Apr 25, 2015 at 12:41 AM, Brendan Eich <brendan@secure.meer.net> wrote:
> Step where you need to, to avoid falling over :-P.

Fair. I filed

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28566

on adding a structured clone API.


> 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.

Dmitry and I worked a bit on

  https://github.com/dslomov-chromium/ecmascript-structured-clone

at some point to clean up things and integrate it with ECMAScript, but
it hasn't really gone anywhere so far.


-- 
https://annevankesteren.nl/
Received on Monday, 27 April 2015 09:54:35 UTC

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