W3C home > Mailing lists > Public > public-web-intents@w3.org > November 2011

Re: Transferable Objects, was: Re: Web Messaging Intents, was: Re: [DRAFT] Web Intents Task Force Charter

From: Greg Billock <gbillock@google.com>
Date: Tue, 22 Nov 2011 10:21:44 -0800
Message-ID: <CAAxVY9dh-tvKikbJQ1j6iX6EuBPGHM_wjA1nKKnRfhnB9Jckyw@mail.gmail.com>
To: Rich Tibbett <richt@opera.com>
Cc: WebIntents <public-web-intents@w3.org>
On Tue, Nov 22, 2011 at 8:10 AM, Rich Tibbett <richt@opera.com> wrote:

>
> Of course! Until recently MessagePort wasn't compatible with the
> structured clone algorithm but since it has recently come to implement
> Transferable it has become compatible with that algorithm, making your
> example work and negating the need for a fourth parameter specifically for
> Transferable objects.
>
> Thanks for the explanation. This is helpful. I hope we can document this
> level of detail in a specification soon.


In our proposal doc (
https://sites.google.com/a/chromium.org/dev/developers/design-documents/webintentsapi<https://sites.google.com/a/chromium.org/dev/developers/design-documents/webintentsapi?pli=1>)
we have documented this payload |data| parameter as a structured clone. I
think you're totally right that this should go into the spec. It makes for
really good interation with other platform features like ports, blobs, and
stuff we haven't thought up yet. :-)

-Greg
Received on Tuesday, 22 November 2011 18:22:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:45 UTC