On Wed, Mar 11, 2009 at 2:30 PM, Drew Wilson atwil...@google.com wrote:
Mark, I won't pretend to completely understand the use cases you're
describing as I'm not familiar with the prior work you've cited. But my
understanding of the postMessage() API is that they are primarily useful for
Yes, it sends a clone, but the source port becomes unentangled (inactive) -
step 5 of the clone a port specification reads:
Entanglehttp://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#entangle
the remote port and new port objects. The original port object will be
unentangled by
Posted first at public-html-comments, but that list seems silent. I
have received suggestions to repost here.
Message 1 of 2, from
http://lists.w3.org/Archives/Public/public-html-comments/2009Mar/0001.html:
Currently, HTML5's postMessage may transfer some amount of data in the
message, and up to
Message 2 of 2, from
http://lists.w3.org/Archives/Public/public-html-comments/2009Mar/0002.html:
To be concrete about it, I am a member of the Caja team, which is building
an object-capability subset of JavaScript by translation to JavaScript.
Currently, Caja brings object-capabilities only to
