RemoteDocumentMessaging - Revision history

Annevk at 03:20, 23 June 2013

2013-06-23T03:20:29Z

← Older revision		Revision as of 03:20, 23 June 2013
Line 33:		Line 33:
	channel.postMessage("I think, therefore I am.");		channel.postMessage("I think, therefore I am.");
	</pre>		</pre>

			==Notes==

			You can already accomplish this through localStorage as that broadcasts storage events: http://bens.me.uk/2013/localstorage-inter-window-messaging Something that does not involve synchronous IO would probably be better though.

	[[Category:Proposals]]		[[Category:Proposals]]

Abarth: /* Examples */

2013-06-21T21:15:25Z

Examples

← Older revision		Revision as of 21:15, 21 June 2013
Line 22:		Line 22:

	<pre>		<pre>
			// The channel name, "deep-thoughts", is scoped to the current origin.
	var channel = new BroadcastChannel("deep-thoughts");		var channel = new BroadcastChannel("deep-thoughts");

Abarth: /* Examples */

2013-06-21T20:47:25Z

Examples

← Older revision		Revision as of 20:47, 21 June 2013
Line 22:		Line 22:

	<pre>		<pre>
	var channel = new BroadcastChannel("~~channel~~-~~name~~");		var channel = new BroadcastChannel("deep-thoughts");

	channel.addEventListener("message", function(message) {		channel.addEventListener("message", function(message) {

Abarth: /* Specification */

2013-06-21T20:46:36Z

Specification

← Older revision		Revision as of 20:46, 21 June 2013
Line 11:		Line 11:
	<pre>		<pre>
	[Constructor(DOMString name)]		[Constructor(DOMString name)]
	interface BroadcastChannel {		interface BroadcastChannel : EventTarget {
	void postMessage(any message);		void postMessage(any message);
	void close();		void close();

			attribute EventHandler onmessage;
	};		};
	</pre>		</pre>

Abarth: /* Specification */

2013-06-21T20:45:36Z

Specification

← Older revision		Revision as of 20:45, 21 June 2013
Line 12:		Line 12:
	[Constructor(DOMString name)]		[Constructor(DOMString name)]
	interface BroadcastChannel {		interface BroadcastChannel {
	void postMessage(any message~~, optional sequence<Transferable> transfer~~);		void postMessage(any message);
	void close();		void close();
	};		};

Abarth: /* Specification */

2013-06-21T20:45:22Z

Specification

← Older revision		Revision as of 20:45, 21 June 2013
Line 10:		Line 10:

	<pre>		<pre>
	~~partial~~ interface ~~Window~~ {		[Constructor(DOMString name)]
	~~MessagePort connectTo~~(~~DOMString target~~);		interface BroadcastChannel {
			void postMessage(any message, optional sequence<Transferable> transfer);
			void close();
	};		};
	</pre>		</pre>

	The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).

	~~# Create a new MessagePort object owned by the global object of the incumbent script. Let this be the initiator's port.~~
	~~# Return the initiator's port and perform the remaining steps asynchronously.~~
	# Spin the event loop until a browsing context with name <code>target</code> has the same effective script origin as the incumbent script has an active document whose ready state has reached "interactive". Let this document be the responder's document.
	~~# Create a new MessagePort object owned by the global object of the responder's document. Let this be the responder's port.~~
	~~# Entangle the initiator's port and the responder's port.~~
	# Create a trusted event that uses the MessageEvent interface, with the name connect, which does not bubble, is not cancelable, has no default action, has a data attribute whose value is initialized to the empty string, has a ports attribute whose value is initialized to a read only array containing only the responder's port, and has a source attribute whose value is initialized to the responder's port, and queue a task to dispatch the event at global object of the responder's document.

	==Examples==		==Examples==

Abarth: /* Examples */

2013-06-21T20:42:50Z

Examples

← Older revision		Revision as of 20:42, 21 June 2013
Line 25:		Line 25:

	==Examples==		==Examples==

	~~===Listener===~~

	~~<pre>~~
	~~window.addEventListener("connect", function(message) {~~
	~~// message.source is a MessagePort we can use to talk to the remote message, just like in a shared worker.~~
	~~var remote = message.source;~~
	~~remote.postMessage("Welcome!");~~
	~~// You can call remote.addEventListener("message", ... ) to continue communicating with the remote window.~~
	~~}, false);~~

	~~// Naming your window makes you discoverable by other documents in your origin.~~
	~~window.name = "the-listener";~~
	~~</pre>~~

	~~===Sender===~~

	<pre>		<pre>
	var ~~port~~ = ~~window.connectTo~~("~~the~~-~~listener~~");		var channel = new BroadcastChannel("channel-name");

	~~port~~.addEventListener("message", function(message) {		channel.addEventListener("message", function(message) {
	~~if (~~message.~~data == "Welcome!")~~		// Do something interesting with \|message\|, which is a MessageEvent.
	~~alert("Success!);~~
	}, false);		}, false);

	~~port~~.~~start~~();		// Send a message to each other BroadcastChannel instance with the same channel
			// name in the same origin.
			channel.postMessage("I think, therefore I am.");
	</pre>		</pre>

	[[Category:Proposals]]		[[Category:Proposals]]

Abarth at 18:46, 21 June 2013

2013-06-21T18:46:13Z

← Older revision		Revision as of 18:46, 21 June 2013
Line 17:		Line 17:
	The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).		The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).

	# Create a new MessagePort object owned by the global object of the incumbent script. Let this be the ~~outside~~ port.		# Create a new MessagePort object owned by the global object of the incumbent script. Let this be the initiator's port.
	# Return the ~~outside~~ port and ~~continue executing~~ the ~~following~~ steps asynchronously.		# Return the initiator's port and perform the remaining steps asynchronously.
			# Spin the event loop until a browsing context with name <code>target</code> has the same effective script origin as the incumbent script has an active document whose ready state has reached "interactive". Let this document be the responder's document.
			# Create a new MessagePort object owned by the global object of the responder's document. Let this be the responder's port.
			# Entangle the initiator's port and the responder's port.
			# Create a trusted event that uses the MessageEvent interface, with the name connect, which does not bubble, is not cancelable, has no default action, has a data attribute whose value is initialized to the empty string, has a ports attribute whose value is initialized to a read only array containing only the responder's port, and has a source attribute whose value is initialized to the responder's port, and queue a task to dispatch the event at global object of the responder's document.

	==Examples==		==Examples==

Abarth at 18:34, 21 June 2013

2013-06-21T18:34:33Z

← Older revision		Revision as of 18:34, 21 June 2013
Line 11:		Line 11:
	<pre>		<pre>
	partial interface Window {		partial interface Window {
	MessagePort? connectTo(DOMString target);		MessagePort connectTo(DOMString target);
	};		};
	</pre>		</pre>

	The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).		The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).

			# Create a new MessagePort object owned by the global object of the incumbent script. Let this be the outside port.
			# Return the outside port and continue executing the following steps asynchronously.

	==Examples==		==Examples==

Abarth at 18:30, 21 June 2013

2013-06-21T18:30:50Z

← Older revision		Revision as of 18:30, 21 June 2013
Line 15:		Line 15:
	</pre>		</pre>

	The <code>connectTo</code> method ~~instructs the user agent~~ to ~~search for~~ a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).		The <code>connectTo</code> method opens a message port to a browsing context with name <code>target</code> within the caller's origin (although not necessarily within the caller's unit of related browsing contexts).

	~~If the user agent finds such a browsing context, the user agent creates two entangled message ports. The first port is returned to the caller ..~~.

	==Examples==		==Examples==
Line 24:		Line 22:

	<pre>		<pre>
	window.addEventListener("~~message~~", function(message) {		window.addEventListener("connect", function(message) {
	~~if (message.origin != location.origin)~~
	~~return;~~
	~~if (message.data != "Hi there!")~~
	~~return;~~
	// message.source is a MessagePort we can use to talk to the remote message, just like in a shared worker.		// message.source is a MessagePort we can use to talk to the remote message, just like in a shared worker.
	var remote = message.source;		var remote = message.source;
	remote.postMessage("~~Thanks for the message~~!");		remote.postMessage("Welcome!");
	// You can call remote.addEventListener("message", ... ) to continue communicating with the remote window.		// You can call remote.addEventListener("message", ... ) to continue communicating with the remote window.
	}, false);		}, false);
Line 42:		Line 36:

	<pre>		<pre>
	var ~~remote~~ = window.connectTo("the-listener");		var port = window.connectTo("the-listener");

	~~remote~~.addEventListener("message", function(message) {		port.addEventListener("message", function(message) {
	if (message.data == "~~Thanks for the message~~!")		if (message.data == "Welcome!")
	alert("Success!);		alert("Success!);
	}, false);		}, false);

	~~remote~~.~~postMessage~~(~~"Hi there!"~~);		port.start();
	</pre>		</pre>

	[[Category:Proposals]]		[[Category:Proposals]]