BrowserID Key Wrapping: Difference between revisions

BrowserID Key Wrapping (view source)

26 bytes added , 19 January 2012

668

edits

@@ Line 46: / Line 46: @@
 === Communication with BrowserID ===
-In the diagrams below, communication is shown between two client-side (in-browser) domains: the service and BrowserID. Communication between these two domains is done using postMessage across these origins. The BrowserID implementation will eventually be built-in, thus part of the browser chrome rather than a second content origin. In any case, the communication pattern is asynchronous, <tt>postMessage()</tt> style
+In the diagrams below, communication is shown between the client-side of the web service and the BrowserID implementation in the client. If BrowserID is delivered by BrowserID.org, this communication is implemented over postMessage() between the service's origin and the BrowserID origin. If BrowserID is built into the user agent, this communication is simply the native DOM API defined above, with BrowserID implemented in the browser chrome.
 === User Key ===