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

Re: What changes to Web Messaging spec are proposed? [Was: Re: Using ArrayBuffer as payload for binary data to/from Web Workers]

From: David Levin <levin@chromium.org>
Date: Thu, 2 Jun 2011 13:27:01 -0700
Message-ID: <BANLkTin-=vnM=TjfwVG9Aoz2rt2LpARWd-VvFaPwZq=uP5nR1g@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps <public-webapps@w3.org>
On Thu, Jun 2, 2011 at 1:13 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 6/2/11 3:53 PM, David Levin wrote:
>
>> The mechanism:
>>
>>    * needs to have an intuitive feel for developers,
>>    * must preserve backwards compatibility,
>>    * should ideally allow the port to function the same regardless of
>>      whether the message was cloned or transferred.
>>
>
> I'm not sure what you mean by that third item...  the obvious meaning,
> which is that clone vs transfer is not black-box observable to the code
> calling postMessage makes no sense.


The receiver of the message is what I meant to say.

My edits lost some of the context.

dave


>  There are three ideas for how to accomplish this:
>>
>
> 4.  Having separate arguments (in some order) for the ports and the list of
> objects to transfer.
>
> -Boris
>
>
Received on Thursday, 2 June 2011 20:27:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT