{"json_modified": "2016-03-28T08:42:46.619971", "uuid": "e7286f70-e1d7-4f8e-98e1-da71a3623f7f", "title": "Using channel messaging", "url": "/en-US/docs/Web/API/Channel_Messaging_API/Using_channel_messaging", "tags": ["API", "HTML5", "Tutorial", "MessagePort", "Channel messaging", "MessageChannel"], "translations": [], "modified": "2015-11-25T13:31:17", "label": "Using channel messaging", "localization_tags": [], "locale": "en-US", "id": 135211, "last_edit": "2015-11-25T13:31:14", "summary": "The <a href=\"/en-US/docs/Web/API/Channel_Messaging_API\">Channel Messaging API</a> allows two separate scripts running in different browsing contexts attached to the same document (e.g., two IFrames, or the main document and an IFrame, or two documents via a <a href=\"/en-US/docs/Web/API/SharedWorker\" title=\"The SharedWorker interface represents a specific kind of worker that can be accessed from several browsing contexts, such as several windows, iframes or even workers. They implement an interface different than dedicated workers and have a different global scope, SharedWorkerGlobalScope.\"><code>SharedWorker</code></a>) to communicate directly, passing messages between one another through two-way channels (or pipes) with a port at each end. In this article we'll explore the basics of using this technology.", "sections": [{"id": "Quick_Links", "title": null}, {"id": "Use_cases", "title": "Use cases"}, {"id": "Simple_examples", "title": "Simple examples"}, {"id": "Creating_the_channel", "title": "Creating the channel"}, {"id": "Receiving_the_port_and_message_in_the_IFrame", "title": "Receiving the port and message in the IFrame"}, {"id": "Receiving_the_confirmation_in_the_main_page", "title": "Receiving the confirmation in the main page"}, {"id": "Specifications", "title": "Specifications"}, {"id": "Browser_compatibility", "title": "Browser compatibility"}, {"id": "See_also", "title": "See also"}], "slug": "Web/API/Channel_Messaging_API/Using_channel_messaging", "review_tags": []}