Refer toĪll cross-domain local storage access is disabled by default with Safari 7+. then ( function ( ) ) ĪPI breaking changes were introduced in both 0.6 and 1.0. This only restricts access on a per-domain or web app level. User has full control of their local storage data - it's still client data. The set of permissionsĪre enforced thanks to the same-origin policy. ThisĪllows multiple clients to access and share the data located in a single store.Ĭare should be made to limit the origins of the bidirectional communication.Īs such, when initializing the hub, an array of permissions objects is passed.Īny messages from clients whose origin does not match the pattern are ignored,Īs well as those not within the allowed set of methods. The clients then load said hub over an embedded iframeĪnd post messages, requesting data to be stored, retrieved, and deleted. The hubs reside on a host of choice and interact directly with How does it work? The library is divided into two types of components: hubsĪnd clients. For a list of compatible browsers, refer to To LocalStorage, which is available in IE 8+, FF 3.5+, Chrome 4+, as well as a Shave a few KB off your request headers by avoiding cookies. For a client-heavy application, you can potentially Unlike cookies, your client-side data isn't limited to a few kilobytes - you The library is a convenient alternative to sharing a root domain cookie. Windows/tabs, across a variety of domains, to share a single localStorage. Cross domain local storage, with permissions.
0 kommentar(er)
