W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2012

Clarification requested: Callback in "simple API"

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 27 Mar 2012 13:43:05 +0200
Message-ID: <4F71A7C9.7070806@alvestrand.no>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
A clarification request....

the signalling callback in jsep-easy1 is described as:

ThesignalingCallbackargument is a method that will be invoked when the 
user agent needs to send a message to the other host over the signaling 
channel. When the callback is invoked, convey its first argument (a 
string) to the other peer using whatever method is being used by the Web 
application to relay signaling messages.

However, the message description says:

The|PeerConnection|id 
<http://lists.w3.org/Archives/Public/public-webrtc/2012Mar/att-0049/webrtc_jsep_easy1-2012-03-14.html#peerconnection-id>is 
included in every generated signaling message to differentiate locally 
produces signaling messages from remotely produced ones.

and:

   1.

      Iftypeis acase-sensitivematch to "|OFFER|", andlocalis true, then
      instruct the|PeerConnection|SDP Agent
      <http://lists.w3.org/Archives/Public/public-webrtc/2012Mar/att-0049/webrtc_jsep_easy1-2012-03-14.html#peerconnection-sdp-agent>to
      processsdpas a local description of type offer and abort these steps.

How is it intended that the recipient of the signalingCallback know when 
to send the message to the other host, and when to process it locally?

(note: I am not stating an opinion on the API at this time; I am waiting 
for other WG members to do that. This is a question for clarification.)

                     Harald
Received on Tuesday, 27 March 2012 11:43:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 11:43:38 GMT