A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

RemoteDocumentMessaging: Difference between revisions

From WHATWG Wiki
Jump to navigation Jump to search
(Created page with "==Overview== This document describes a proposal for discovering and communicating with "remote" documents. In particular, this proposal lets a web page communicate with anot...")
 
No edit summary
Line 6: Line 6:


The user opens the same word processing document hosted by a document editing web site in two different browser windows.  The document editing web site wants to ensure that edits in one window a reflected in the other window without needing to round-trip through the server (e.g., because the user is offline).  Unfortunately, the documents are in different units of related browsing contexts, which means the two documents cannot form a direct script connection.  Using remote document messaging, the two documents can discover each other and update each other about edits performed by the user.
The user opens the same word processing document hosted by a document editing web site in two different browser windows.  The document editing web site wants to ensure that edits in one window a reflected in the other window without needing to round-trip through the server (e.g., because the user is offline).  Unfortunately, the documents are in different units of related browsing contexts, which means the two documents cannot form a direct script connection.  Using remote document messaging, the two documents can discover each other and update each other about edits performed by the user.
==Examples==
===Listener===
<pre>
window.addEventListener("message", function(message) {
  if (message.origin != location.origin)
    return;
  // message.source is a MessagePort we can use to talk to the remote message, just like in a shared worker.
  var remoteMessagePort = message.source;
  remoteMessagePort.postMessage("Thanks for the message!");
}, false);
window.name = "the-listener";
</pre>
[[Category:Proposals]]

Revision as of 18:04, 21 June 2013

Overview

This document describes a proposal for discovering and communicating with "remote" documents. In particular, this proposal lets a web page communicate with another document even if the web page does not have a direct script connection to that document.

Use Cases

The user opens the same word processing document hosted by a document editing web site in two different browser windows. The document editing web site wants to ensure that edits in one window a reflected in the other window without needing to round-trip through the server (e.g., because the user is offline). Unfortunately, the documents are in different units of related browsing contexts, which means the two documents cannot form a direct script connection. Using remote document messaging, the two documents can discover each other and update each other about edits performed by the user.

Examples

Listener

window.addEventListener("message", function(message) {
  if (message.origin != location.origin)
    return;
  // message.source is a MessagePort we can use to talk to the remote message, just like in a shared worker.
  var remoteMessagePort = message.source;
  remoteMessagePort.postMessage("Thanks for the message!");
}, false);

window.name = "the-listener";