Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Message Channel API Article #626

Closed
kongaraju opened this issue Sep 30, 2013 · 3 comments
Closed

Message Channel API Article #626

kongaraju opened this issue Sep 30, 2013 · 3 comments

Comments

@kongaraju
Copy link

I would like to contribute to this repository with an article on Message Channel API.

@ebidel
Copy link
Contributor

ebidel commented Oct 8, 2013

Please propose an outline

@kongaraju
Copy link
Author

Javascript Thead Communication

Message Channel API is a part of Web Messaging specification . Message Channel allows to communicate two independent scripts like workers. It helps to transfer messages to the other end without any media, both the threads can communicate directly via ports. Array of ports can be sent using ports property of event.

Ports send messages using postMessage and receive messages using onmessage . start enables the message port and close will terminates. It can be stored locally and used repeatedly as you needed.

Message Channel API helps to build heavy applications using javascript and is very useful to increase speed of javascript engines.

Table of contents

  • Introducing thread communication : Javascript
  • Message Channel API
  • Getting Started
  • Communication and Message Passing
  • Transferable objects
  • Scope
  • Use Cases
  • Demos

@ebidel

@PaulKinlan
Copy link
Member

I do like the idea of this article, specifically how and when it should be used (which I think should be at the top of the article). I am also very interested in how this works on mobile (ios, android and safari) and what developers should do if there is no support for the api (i.e, windows phone)

kongaraju added a commit to kongaraju/www.html5rocks.com that referenced this issue Jan 30, 2016
Issue html5rocks#626 raised some time back regarding this.

html5rocks#626
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants