I use it to communicate between tabs. For example, when capturing an electronic signature, we open the document to be signed in a new tab. When they submit the signature, I message the main tab to let it know that the signature has been submitted. This allows me to take further actions on the main tab without having to do some convoluted server-side check via polling.
It's intended for cross-domain messaging. One big example would be Facebook apps, which currently have to communicate with Facebook via a convoluted manner as they live on a separate domain in an iframe.
跨域支持将使这一点得到更广泛的采用。因为不是每个人都会建立自己的响应式 Web 服务器和实时 Web 应用程序，跨域支持将允许那些不太动态的网站集成来自第三方的新功能。
I think all these technologies enable a more responsive web design. It's just like the AJAX transition: Before the transition, users expect to see the whole page refresh; After the transition, users understand the page can be updated partially.
When the new transition is finished, users will realize that content on the page could be real-time data. That means a user is not only interacting with a website (and then wait for other users to interact with the same website). He or she could be interacting with other users because it's real-time interaction over the website.
Cross-domain support will make this more widely adopted. Because not everybody will set up their own responsive web server and real-time web application, cross-domain support will allow those not-so-dynamic websites to integrate new features from 3rd-parties.
I recently found a good use case for Web Messaging. Many web apps are starting to authenticate using Facebook, so they open another tab with a Facebook login and communicate with the its contents.
Got a better use case? If so, I'll unselect my answer.
发布评论
评论（4）
我用它在选项卡之间进行通信。例如，在捕获电子签名时，我们在新选项卡中打开要签名的文档。当他们提交签名时，我会向主选项卡发送消息，让它知道签名已提交。这允许我在主选项卡上采取进一步的操作，而不必通过轮询进行一些复杂的服务器端检查。
I use it to communicate between tabs. For example, when capturing an electronic signature, we open the document to be signed in a new tab. When they submit the signature, I message the main tab to let it know that the signature has been submitted. This allows me to take further actions on the main tab without having to do some convoluted server-side check via polling.
它旨在用于跨域消息传递。一个重要的例子是 Facebook 应用程序，目前它们必须通过一种复杂的方式与 Facebook 进行通信，因为它们位于 iframe 中的单独域中。
It's intended for cross-domain messaging. One big example would be Facebook apps, which currently have to communicate with Facebook via a convoluted manner as they live on a separate domain in an iframe.
我认为所有这些技术都可以实现更具响应性的网页设计。就像AJAX转换一样：在转换之前，用户期望看到整个页面刷新；在转换之前，用户期望看到整个页面刷新；转换后，用户了解到页面可以部分更新。
当新的转换完成后，用户将意识到页面上的内容可以是实时数据。这意味着用户不仅与网站交互（然后等待其他用户与同一网站交互）。他或她可以与其他用户交互，因为这是通过网站进行的实时交互。
跨域支持将使这一点得到更广泛的采用。因为不是每个人都会建立自己的响应式 Web 服务器和实时 Web 应用程序，跨域支持将允许那些不太动态的网站集成来自第三方的新功能。
I think all these technologies enable a more responsive web design. It's just like the AJAX transition: Before the transition, users expect to see the whole page refresh; After the transition, users understand the page can be updated partially.
When the new transition is finished, users will realize that content on the page could be real-time data. That means a user is not only interacting with a website (and then wait for other users to interact with the same website). He or she could be interacting with other users because it's real-time interaction over the website.
Cross-domain support will make this more widely adopted. Because not everybody will set up their own responsive web server and real-time web application, cross-domain support will allow those not-so-dynamic websites to integrate new features from 3rd-parties.
我最近发现了一个很好的网络消息传递用例。许多网络应用程序开始使用 Facebook 进行身份验证，因此它们使用 Facebook 登录名打开另一个选项卡并与其内容进行通信。
有更好的用例吗？如果是这样，我将取消选择我的答案。
I recently found a good use case for Web Messaging. Many web apps are starting to authenticate using Facebook, so they open another tab with a Facebook login and communicate with the its contents.
Got a better use case? If so, I'll unselect my answer.