Confirmed users
216
edits
WebAPI/PresentationAPI:CoreService: Difference between revisions
WebAPI/PresentationAPI:CoreService (view source)
Revision as of 03:01, 21 April 2016
, 21 April 2016→Call Flow Example: add sequence diagram for receiving presentation request
Junior Hsu (talk | contribs) |
(→Call Flow Example: add sequence diagram for receiving presentation request) |
||
| Line 45: | Line 45: | ||
# Create a session transport builder: As chrome process ready (receive control channel|NotifyOpened| for controller; receive control channel |OnOffer| and receiver page ready |NotifyResponderReady| for presenter), |PresentationSessionInfo| create a transport builder to establish a transport. | # Create a session transport builder: As chrome process ready (receive control channel|NotifyOpened| for controller; receive control channel |OnOffer| and receiver page ready |NotifyResponderReady| for presenter), |PresentationSessionInfo| create a transport builder to establish a transport. | ||
# Build a transport in content process: The transport builder is |PresentationParent| hooked by first step. It will triggered an IPC call to |PresentationIPCService| and build the underlying RTCDataChannel in the content process. It will call back to |PresentationService| the result of building. | # Build a transport in content process: The transport builder is |PresentationParent| hooked by first step. It will triggered an IPC call to |PresentationIPCService| and build the underlying RTCDataChannel in the content process. It will call back to |PresentationService| the result of building. | ||
=== Controlling UA === | |||
==== start session ==== | |||
==== close and resume connection === | |||
==== terminate connection ==== | |||
=== Receiving UA === | |||
==== handle presentation request === | |||
* establishing TCP Transport | |||
[[File:CoreService Flow handle session request.png]] | |||