Confirmed users
216
edits
WebAPI/PresentationAPI:CoreService: Difference between revisions
Jump to navigation
Jump to search
→Call Flow Example: add sequence diagram for message transmission on TCP transport
(→Receiving UA: separate request handling and connection monitoring) |
(→Call Flow Example: add sequence diagram for message transmission on TCP transport) |
||
| 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. | ||
==== Message Transmission for TCPSessionTransport ==== | |||
[[File:CoreService Flow message transmission for TCP transport.png|thumb|650px|sequence diagram of message transmission over TCPPresentationTransport]] | |||
* message transmission over TCPPresentationTransport | |||
# when connection.send is invoked, PresentationService will delegate the message content to corresponding session info object | |||
## session info object will used the associated TCPPresentationTransport object for sending message to remote peer | |||
# when incoming message is received by TCPPresentationTransport, the message will be delegate to corresponding PresentationConnection object | |||
## onmessage event will be fired on that PresentationConnection object. | |||
=== Controlling UA === | === Controlling UA === | ||