Re: Issue 1858: the astonishing behavior of transceiver.stop

• From: Harald Alvestrand <harald@alvestrand.no>
• Date: Sat, 21 Jul 2018 17:48:24 +0200
• To: public-webrtc@w3.org
• Message-ID: <2b0daeab-cb2f-dcf5-c276-a6a46ab697e1@alvestrand.no>

Den 12. juli 2018 13:51, skrev Iñaki Baz Castillo:
> On Thu, 12 Jul 2018 at 13:38, Harald Alvestrand <harald@alvestrand.no> wrote:
>>
>> - "SDP has special semantics for port=0 on an M-line"
>> - "We've got to figure out how to set that! Since m-lines are
>> transceivers, transceiver.<something>. BTW, what does it mean?"
>> - "It means that the m-line isn't used any more - people use it to stop
>> things"
>> - "OK, let's call it transceiver.stop() then".
> 
> This is, literally, making an API not because it's useful but just to
> conform to some strange SDP semantic rules.
> 
> I hope brilliant minds here do not waste too much time in this useless stuff.
> 

Since the transceiver is inherently an SDP construct, I am all in favor
of defining its behavior as "do what the SDP-related specs say". Let's
not waste time being creative here.

Received on Saturday, 21 July 2018 15:48:52 UTC