W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2018

Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 May 2018 17:24:20 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-391431069-1527096259-sysbot+gh@w3.org>

Could implementations maybe create this m-line behind the user's back, and never expose it as a "transceiver" to JS?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1858#issuecomment-391431069 using your GitHub account

Received on Wednesday, 23 May 2018 17:24:23 UTC

This message: [ Message body ]
Next message: Taylor Brandstetter via GitHub: "Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?"
Previous message: Taylor Brandstetter via GitHub: "Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?"
Maybe in reply to: jan-ivar via GitHub: "Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?"
Next in thread: Taylor Brandstetter via GitHub: "Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:44 UTC