- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Mar 2015 09:49:38 +0000
- To: public-secondscreen@w3.org
The following commits were just pushed by drott to https://github.com/w3c/presentation-api: * 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 https://github.com/w3c/presentation-api/commit/9317d63dde0c953402167d22ece300805da16f68 * Corrections. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/97b13cee58ab39821d82cb23bcabd1f96d1adae3 * Keep issue reference in, keep EventHandler link. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/9442ca349eb4382e03977fb5f017579308126e42 * > 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; Changed. >> (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 https://github.com/w3c/presentation-api/commit/9d7c39f5e424ec6f66986ef593d6633a2eb59a43 * event firing impoved by Dominik Röttsches https://github.com/w3c/presentation-api/commit/6b715933a8554a1b196b3e7e37f1749bd2ea5c32 * Typo in note fixed. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/83aebf68feafdae6ccd230721cd17f59f245d308 * Destination browsing context as span. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/f13ce46b0ce388f5ff75a8fccca2fcea15ed4055 * Mention messageType argument. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/76d18d266d44846f3df75e108568ab1bf1a3e36c * Additional nits fixed. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/11bc71132a40bc71ff1115d96b637a1c138ce341 * Merge pull request #62 from drott/postmessage Define postMessage and onmessage algorithms Modeled after WebSockets interface. Fixes issue #46. by Dominik Röttsches https://github.com/w3c/presentation-api/commit/e2ce0bf90f80fda75fbd3b090d1509df051d06e4
Received on Tuesday, 10 March 2015 09:49:46 UTC