W3C home > Mailing lists > Public > public-secondscreen@w3.org > March 2015

[presentation-api] new commits pushed by drott

From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Mar 2015 09:49:38 +0000
To: public-secondscreen@w3.org
Message-ID: <push-e2ce0bf90f80fda75fbd3b090d1509df051d06e4-1425980976-sysbot+gh@w3.org>
The following commits were just pushed by drott to 

* First version of postMessage and onmessage algorithms

Modeled after WebSockets behavior.

TODO: Fix references to ArrayBuffer, Blob, etc.
TODO: Discuss whether we need "binaryType"
  by Dominik Röttsches

* Corrections.
  by Dominik Röttsches

* Keep issue reference in, keep EventHandler link.
  by Dominik Röttsches

* > TODO: Fix references to ArrayBuffer, Blob, etc.

Added, drott's xref repo updated to include TypedArray spec.

> TODO: Discuss whether we need "binaryType"

Left in for now to emulate WebSocket spec.

> TODO: Check trusted event property.

Reference to trusted event added, isTrusted is true since it's a UA 
generated event.

> TODO: Define presentation origin somewhere.

Issue #63 created.

> Does this mean a single invocation of postMessage()?
> I think it would be permissible for the implementation to fragment
> transmission (e.g. to meet the requirements of a network transport)
> of a single message. Can it be clarified?

Tried to clarify this by specifying a "data payload" and an 
implementation specific transport mechanism.

>> presentation message format
> I think of this as a type, not a format;


>> (Set to Binary if data is one of ArrayBuffer or Blob. Set to Text 
if data is of type DOMString)
> This would be clearer as its own step.

Moved to own step.

> Maybe just "to the destination browsing context"? Or have a step 
that defines the destination context for the data?

Defined destination browsing context in separate step.

> What if they have no URL in common?

See above, created issue #63 to discuss origin relationship.

> ...as a DOMString?

Added mention of type here.
  by Dominik Röttsches

* event firing impoved
  by Dominik Röttsches

* Typo in note fixed.
  by Dominik Röttsches

* Destination browsing context as span.
  by Dominik Röttsches

* Mention messageType argument.
  by Dominik Röttsches

* Additional nits fixed.
  by Dominik Röttsches

* Merge pull request #62 from drott/postmessage

Define postMessage and onmessage algorithms

Modeled after WebSockets interface.

Fixes issue #46.
  by Dominik Röttsches
Received on Tuesday, 10 March 2015 09:49:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 March 2015 09:49:46 UTC