668
edits
Identity/Architecture/SignIntoBrowser: Difference between revisions
Identity/Architecture/SignIntoBrowser (view source)
Revision as of 00:41, 21 April 2012
, 21 April 2012→ID-attached Services
| Line 37: | Line 37: | ||
=== ID-attached Services === | === ID-attached Services === | ||
An ID-attached service is a web-based service that takes a BrowserID assertion for login, then provides a particular service whose semantics are defined for that service category. The interface to that ID-attached service is via JavaScript <tt>MessageChannel</tt>: the user-agent loads the ID-attached-service endpoint URL in an (invisible) IFRAME and makes API calls to it using standard <tt>postMessage</tt> mechanics. | An ID-attached service is a web-based service that takes a BrowserID assertion for login, then provides a particular service whose semantics are defined for that service category. The interface to that ID-attached service is via JavaScript <tt>MessageChannel</tt>: the user-agent loads the ID-attached-service endpoint URL in an (invisible) IFRAME and makes API calls to it using standard <tt>postMessage</tt> mechanics. The specifics of the <tt>MessageChannel</tt> calls are defined by the type of service. | ||
For example, an ID-attached Bookmarks Service implementation, be it from Mozilla or Delicious, provides a URL endpoint that expects certain bookmarks-specific calls over the <tt>MessageChannel</tt>. | |||
(Why not REST? Because want to allow the service to do its own authentication and caching.) | (Why not REST? Because want to allow the service to do its own authentication and caching.) | ||
=== User-Agent === | === User-Agent === | ||
== Flow == | == Flow == | ||