668
edits
Identity/Architecture/SignIntoBrowser: Difference between revisions
Jump to navigation
Jump to search
Identity/Architecture/SignIntoBrowser (view source)
Revision as of 04:06, 23 April 2012
, 23 April 2012→Working with an ID-attached service
(→Flow) |
|||
| Line 78: | Line 78: | ||
* set up, in that IFRAME, a <tt>window.channel</tt> field, which is a standard HTML5 <tt>MessageChannel</tt> on which the endpoint can listen for messages and send messages back to the User Agent. | * set up, in that IFRAME, a <tt>window.channel</tt> field, which is a standard HTML5 <tt>MessageChannel</tt> on which the endpoint can listen for messages and send messages back to the User Agent. | ||
* perform a simple message-passing handshake over that MessageChannel to determine if the service needs a BrowserID assertion or if it needs to prompt the user for a login using custom authentication. | |||
* make the service-type specific calls over simple <tt>.emit()</tt> calls to the MessageChannel. | |||