Re: setXxxxxDescription() vs setters/properties [via ORCA - Object-RTC API Community Group]

Wanted to address this:

myConnection.remote.ice.userFrag = XXXXX;
myConnection.remote.ice.passwd = XXXXX;

myConnection.connect();



There's also a different way to do it so you aren't in an intermediate 
state (half set):

myConnection.remote.ice = {userFrag: XXXXX; passwd: XXXXX;};
myConnection.connect();

Just keep that in mind when you are doing the API that getter / setters can take entire objects, not just single one at a time settings.

I think with any API we do, we should remember we'll have to "shim" it over top of the ugly SDP API, so we have to make sure whatever we do can be wired appropriately.

-Robin


PS. Sorry for the late reply, been awfully sick in the past week.


> Iñaki Baz Castillo <mailto:ibc@aliax.net>
> 28 August, 2013 4:54 AM
> Current API defines some methods that expect an Object as argument, or 
> that
> return an Object. For example, when Alice needs to signal Bob that she 
> will send
> an Opus audio track with payload-id=98 and SSRC=1234, something like 
> this should
> be coded: // Alice gets her sending track description/details and 
> signals them
> to Bob: var rtcTrack = rtcConnection.track(audioMediaStreamTrack);
> signalingChannel.send(JSON.stringify({ [...]
>
>
>
> ----------
>
> This post sent on ORCA - Object-RTC API Community Group
>
>
>
> 'setXxxxxDescription() vs setters/properties'
>
> http://www.w3.org/community/orca/2013/08/28/setxxxxxdescription-vs-settersproperties/
>
>
>
> Learn more about the ORCA - Object-RTC API Community Group:
>
> http://www.w3.org/community/orca
>
>
>