Privacy/Reviews/F1A: Difference between revisions

Line 262: Line 262:


Communication with mediator content is tunneled through the mediator class.  There is no direct conduit
Communication with mediator content is tunneled through the mediator class.  There is no direct conduit
between the mediator content and the service content (even though the mediator content could directly access the service iframe).
between the mediator content and the service content (even though the mediator content could directly access the service iframe).  Any call IN will have a response OUT, even if it is an empty response.
 
Each app that supports the share activity implements these calls, each is registered using the registerHandler API.  The built-in apps in Firefox Share have the implemenation.


{| class="wikitable"
{| class="wikitable"
Line 344: Line 346:


'''Communication with mediator class'''  
'''Communication with mediator class'''  
These are all uni-directional calls with the exception of the oauth and sendEmail calls.  The implementation of these APIs are in the openwebapps addon (see servicesapi.js).


{| class="wikitable"
{| class="wikitable"
Line 356: Line 360:
| origin
| origin
| provides the app origin the code we inject into the service iframe, kind of an init for our injected code
| provides the app origin the code we inject into the service iframe, kind of an init for our injected code
|-
| ''Out:''
| service.origin
| none
|
|-
| ''In:''
| service.ready
| none
|
|-
|-
| ''Out:''  
| ''Out:''  
Line 402: Line 396:
|  
|  
|}
|}


=== mediator class  ===
=== mediator class  ===
Confirmed users
169

edits