43
edits
Media/WebRTC/Architecture: Difference between revisions
→Signaling System: localDescription
| Line 219: | Line 219: | ||
=== Signaling System: localDescription === | === Signaling System: localDescription === | ||
Here are two options for implementing this API. | |||
(1). This like the other JSEP API's will be a function on the call object. It will send feature CC_FEATURE_LOCALDESC to the CCAPP thread which will send the message CC_MSG_SETLOCALDESC to GSMTask. The event handler in GSM will return the local SDP string stored with that call's DCB (Dial Control Block). AddStream and CreateOffer or CreateAnswer will need to have been called for this to work successfully. This approach is asynchronous so the SDP will need to be returned similarly to how it is returned for the other JSEP API's, via the UI interface and back through the CCAPP thread. | |||
(2). Another approach would be to not use the the SIPCC APIs and to store the SDP returned from CreateOffer or CreateAnswer in a string in the PeerConnection Interface backend code. This would allow this API to be asynchronous and highly performant. One downside would be that if AddStream or RemoveStream is called the SDP we now store in the PC would not get dynamically updated. | |||
=== Signaling System: remoteDescription === | === Signaling System: remoteDescription === | ||