Synchronized data across all windows without a backend
While other service bus implementations utilize servers to marshal data between applications, the IWC does all of the marshalling local to the browser. The IWC does have backend integration capabilities to persist resources and load application metadata to give the IWC bus awareness of the applications using it.
Simple bi-directional binding. Even cross-framework.
As seen in the bouncing balls above, the IWC can be used to sync
data across applications. This benefits DOM elements as well. With
the IWC being framework-independent, applications built leveraging
various types of frameworks can be syncronized.
Reduce code replication
IWC allows for applications of same and different origins to communicate and share resources without tightly coupling functionality. Leveraging applications that use IWC means less development time, write your application's unique functionality and utilize other applications to handle the common tasks.
Browser Support
IWC does not use any browser plugins or extensions. It leverages modern browser technologies (localStorage and optionally SharedWorkers) and is supported for Firefox 24+, Chrome 37+, and limited support of Internet Explorer 11.
Looking for Previous Release Documentation?
The IWC is an evergrowing effort, and with that documentation, tutorials, and examples must grow as well. The content hosted on this website pertains to the latest release
of the IWC . If working with a previous version, refer to the documentation below:
