Wednesday, 31 July 2013
Tuesday, 30 July 2013
- Re: SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Re: do we want success and failure callbacks on addStream?
- Re: SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Re: Cross posting: Re: [rtcweb] SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- Cross posting: Re: [rtcweb] SDP is not suitable for WebRTC
- Re: [rtcweb] SDP is not suitable for WebRTC
- VS: [rtcweb] SDP is not suitable for WebRTC
- Re: [rtcweb] SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- VS: [rtcweb] SDP is not suitable for WebRTC
Monday, 29 July 2013
- Re: SDP is not suitable for WebRTC
- Re: [rtcweb] SDP is not suitable for WebRTC
- Re: SDP is not suitable for WebRTC
- SDP is not suitable for WebRTC
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: setting bandwidth
- Re: setting bandwidth
- RE: setting bandwidth
- RE: setting bandwidth
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: Recap from WebRTC World
Sunday, 28 July 2013
- Re: setting bandwidth
- Re: setting bandwidth
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
Saturday, 27 July 2013
Friday, 26 July 2013
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: setting bandwidth
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
Thursday, 25 July 2013
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: setting bandwidth
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
Monday, 22 July 2013
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
Thursday, 25 July 2013
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: [rtcweb] Unified plan IPR
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
Wednesday, 24 July 2013
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: sdpMLineIndex required in RTCIceCandidate?
- Re: setting bandwidth
Tuesday, 23 July 2013
Wednesday, 24 July 2013
- Re: Recap from WebRTC World
- Re: setting bandwidth
- Re: setting bandwidth
- Re: muting/hold (was Re: Cisco's position on the WebRTC API)
- Re: do we want success and failure callbacks on addStream?
- RE: Google's position on the WebRTC API
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: setting bandwidth
- Re: do we want success and failure callbacks on addStream?
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: muting/hold (was Re: Cisco's position on the WebRTC API)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- Re: setting bandwidth
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- sdpMLineIndex required in RTCIceCandidate?
- Re: Recap from WebRTC World
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- Re: Recap from WebRTC World
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- Re: Recap from WebRTC World
- Re: SDP wrapper? Object-oriented API?
- Re: Recap from WebRTC World
- Re: setting bandwidth
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- Re: Recap from WebRTC World
- Re: setting bandwidth
- Re: Locus of API discussion
- Re: Cisco's position on the WebRTC API
- Re: Discussing new API proposals
- Re: Recap from WebRTC World
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Locus of API discussion
- Re: Why people munge SDP
- Re: Cisco's position on the WebRTC API
- Re: Why people munge SDP
- Re: Why people munge SDP
- Re: Cisco's position on the WebRTC API
- RE: Locus of API discussion
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Cisco's position on the WebRTC API
- Re: Recap from WebRTC World
- Re: Locus of API discussion
- Re: Locus of API discussion
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Cisco's position on the WebRTC API
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- setting bandwidth
- Pause / resume
- Why people munge SDP
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Cisco's position on the WebRTC API
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Cisco's position on the WebRTC API
- Re: do we want success and failure callbacks on addStream?
- Re: Improve error message when browser denies access to getUserMedia()
- Re: JavaScript API on top of SDP
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: muting/hold (was Re: Cisco's position on the WebRTC API)
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: muting/hold (was Re: Cisco's position on the WebRTC API)
- muting/hold (was Re: Cisco's position on the WebRTC API)
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
- Re: Cisco's position on the WebRTC API
Tuesday, 23 July 2013
- Cisco's position on the WebRTC API
- Re: Unified plan IPR
- Re: Google's position on the WebRTC API
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Re: Google's position on the WebRTC API
- Re: Google's position on the WebRTC API
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Google's position on the WebRTC API
- IPR related to draft-roach-mmusic-unified-plan-00
- Re: Google's position on the WebRTC API
- Re: Google's position on the WebRTC API
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: A view on the current webRTC API and next step...
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Google's position on the WebRTC API
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- A view on the current webRTC API and next step...
- Re: Google's position on the WebRTC API
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Google's position on the WebRTC API
- Re: Proposal: Different specifications for different target audiences
- Google's position on the WebRTC API
Monday, 22 July 2013
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Trickle ICE questions?
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Proposal: Different specifications for different target audiences
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Proposal: Different specifications for different target audiences
- Re: XSF Jingle Special Interest Group.
- XSF Jingle Special Interest Group.
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- RE: Moving forward with SDP control
- Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Re: Trickle ICE questions?
- Trickle ICE questions?
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- server-centric vs. P2P (was Re: Proposal: Different specifications for different target audiences)
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- Re: Moving forward with SDP control
- Re: Proposal: Different specifications for different target audiences
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
Sunday, 21 July 2013
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
Saturday, 20 July 2013
Sunday, 21 July 2013
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
Saturday, 20 July 2013
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: Moving forward with SDP control
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
Friday, 19 July 2013
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: Moving forward with SDP control
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: Proposal: Different specifications for different target audiences
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- RE: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: Proposal: Different specifications for different target audiences
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Proposal: Different specifications for different target audiences
- Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: Moving forward with SDP control
- On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Proposal: Different specifications for different target audiences
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Locus of API discussion
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Locus of API discussion
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
Thursday, 18 July 2013
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Moving forward with SDP control
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- RE: Discussing new API proposals
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: Discussing new API proposals
- RE: [rtcweb] e= lines (Re: Summary of Application Developers' opinions ..)
- Re: Moving forward with SDP control
- RE: Discussing new API proposals
- RE: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Fwd: [rtcweb] e= lines (Re: Summary of Application Developers' opinions ..)
- Re: URL.createObjectURL() for DataChannels
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Re: Moving forward with SDP control
- Re: URL.createObjectURL() for DataChannels
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Discussing new API proposals
Wednesday, 17 July 2013
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: Discussing new API proposals
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: Discussing new API proposals
- RE: Locus of API discussion
- RE: [rtcweb] Locus of API discussion
- RE: Locus of API discussion
- RE: [rtcweb] Locus of API discussion
- RE: Discussing new API proposals
- Re: Discussing new API proposals
- RE: Discussing new API proposals
- RE: Moving forward with SDP control
- RE: Discussing new API proposals
- RE: Discussing new API proposals
- Re: Discussing new API proposals
- RE: Discussing new API proposals
- RE: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Re: Moving forward with SDP control
- Re: JavaScript API on top of SDP
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Discussing new API proposals
- Re: Moving forward with SDP control
- Re: JavaScript API on top of SDP
- Re: URL.createObjectURL() for DataChannels
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
Tuesday, 16 July 2013
- Re: URL.createObjectURL() for DataChannels
- Re: URL.createObjectURL() for DataChannels
- Re: JavaScript API on top of SDP
- Re: JavaScript API on top of SDP
- Re: Membership of this WG (Re: [rtcweb] Summary of Application Developers)
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Re: Membership of this WG (Re: [rtcweb] Summary of Application Developers)
- Re: Locus of API discussion
- Re: Moving forward with SDP control
- Re: Discussing new API proposals
- Re: JavaScript API on top of SDP
- Re: Moving forward with SDP control
- Re: URL.createObjectURL() for DataChannels
- Membership of this WG (Re: [rtcweb] Summary of Application Developers)
- Re: Locus of API discussion
- Moving forward with SDP control
- Discussing new API proposals
- Re: JavaScript API on top of SDP
Monday, 15 July 2013
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: JavaScript API on top of SDP
- Re: JavaScript API on top of SDP
- Re: DOM Futures
- Re: JavaScript API on top of SDP
- Re: JavaScript API on top of SDP
- Be vewy, vewy qwiet...
- RE: JavaScript API on top of SDP
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: DOM Futures
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: JavaScript API on top of SDP
- Re: DOM Futures
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: DOM Futures
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- RE: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
- URL.createObjectURL() for DataChannels
Sunday, 14 July 2013
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures
- Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
Saturday, 13 July 2013
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures
- Re: DOM Futures (was: Mediastream Recording implementation)
- DOM Futures (was: Mediastream Recording implementation)
Friday, 12 July 2013
- Re: do we want success and failure callbacks on addStream?
- Re: [rtcweb] Locus of API discussion
- do we want success and failure callbacks on addStream?
Thursday, 11 July 2013
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
Wednesday, 10 July 2013
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Improve error message when browser denies access to getUserMedia()
- Re: Improve error message when browser denies access to getUserMedia()
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
Tuesday, 9 July 2013
- Re: Locus of API discussion
- Re: Locus of API discussion
- Re: [rtcweb] Locus of API discussion
- Re: [rtcweb] Locus of API discussion
- Re: [rtcweb] Locus of API discussion
- RE: [rtcweb] Locus of API discussion
- Improve error message when browser denies access to getUserMedia()
- Re: Locus of API discussion
- Re: Locus of API discussion
- Re: Locus of API discussion
- Re: Locus of API discussion
- Locus of API discussion
- TPAC Registration open
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
Monday, 8 July 2013
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: WebRTC Web APIs for On-board Multimedia Devices Handling and Control
- Re: Expose capabilities / Allow for IP:Post based connections / Better abstraction
- WebRTC Web APIs for On-board Multimedia Devices Handling and Control
Saturday, 6 July 2013
- Expose capabilities / Allow for IP:Post based connections / Better abstraction
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- RE: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
Friday, 5 July 2013
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: [SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
Wednesday, 3 July 2013
Thursday, 4 July 2013
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
Wednesday, 3 July 2013
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
- Re: API design
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- [Bug 22428] Please unify the WebSocket and RTCDataChannel "readyState". enum RTCDataChannelState { "connecting", "open", "closing", "closed" }; VS const unsigned short CONNECTING = 0 [...]
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
- Re: API design
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
Tuesday, 2 July 2013
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- [Bug 22428] Please unify the WebSocket and RTCDataChannel "readyState". enum RTCDataChannelState { "connecting", "open", "closing", "closed" }; VS const unsigned short CONNECTING = 0 [...]
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- RE: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- VS: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: VS: Teleco Integrators vs Web Developers vs Browser Implementers
- VS: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
- [Bug 20819] no priority API