Saturday, 29 June 2013
- 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
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
Friday, 28 June 2013
- Re: Teleco Integrators vs Web Developers vs Browser Implementers
- Re: API design
- 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: API design
- 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
- Teleco Integrators vs Web Developers vs Browser Implementers
- Re: Recap from WebRTC World
Thursday, 27 June 2013
- Re: Recap from WebRTC World
- Re: API design
- Re: API design
- Re: API design
- Re: Mandatory vs optional codecs
- API design
- Re: Mandatory vs optional codecs
- Re: Mandatory vs optional codecs
- Re: Mandatory vs optional codecs
- Re: Mandatory vs optional codecs
- Mandatory vs optional codecs
- Re: Recap from WebRTC World
- Re: Recap from WebRTC World
- Re: Recap from WebRTC World
- Recap from WebRTC World
- Re: Operations in invalid states: Exceptions don't make sense.
Wednesday, 26 June 2013
- RE: Operations in invalid states: Exceptions don't make sense.
- Re: Is DataChannel label unique?
- Re: Is DataChannel label unique?
Tuesday, 25 June 2013
Wednesday, 26 June 2013
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
Tuesday, 25 June 2013
- Re: Is DataChannel label unique?
- Re: Operations in invalid states: Exceptions don't make sense.
- [Bug 22442] New: Bug in section 8.1.3 Verifying Assertions
- [Bug 22441] New: Bug in section 8.1.2 Requesting Assertions
Monday, 24 June 2013
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- RE: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Re: Simultaneous Peer Connections
- Simultaneous Peer Connections
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- RE: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
Sunday, 23 June 2013
Friday, 21 June 2013
Thursday, 20 June 2013
- Re: Alternative to the offer/answer mechanism
- Fwd: Alternative to the offer/answer mechanism
- RE: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Re: SDP wrapper? Object-oriented API?
- Re: Alternative to the offer/answer mechanism
- RE: Alternative to the offer/answer mechanism
- Re: SDP wrapper? Object-oriented API?
- Re: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- RE: Operations in invalid states: Exceptions don't make sense.
- [Bug 20820] congestion control of data and audio/video
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Alternative to the offer/answer mechanism
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- CfC: publish FPWD of "MediaStream Image Capture"; deadline June 30
Wednesday, 19 June 2013
- Re: Alternative to the offer/answer mechanism
- Re: Alternative to the offer/answer mechanism
- Alternative to the offer/answer mechanism
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- VS: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- [Bug 20820] congestion control of data and audio/video
- [Bug 20819] no priority API
- RE: SDP wrapper? Object-oriented API?
- RE: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- RE: SDP wrapper? Object-oriented API?
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: SDP wrapper? Object-oriented API?
Tuesday, 18 June 2013
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: Operations in invalid states: Exceptions don't make sense.
- RE: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: Operations in invalid states: Exceptions don't make sense.
Monday, 17 June 2013
- Re: quibble on terminology
- quibble on terminology
- Re: SDP wrapper? Object-oriented API?
- Re: How to know if a given track or media stream is being transmitted
- RE: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: How to know if a given track or media stream is being transmitted
- Re: Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: SDP wrapper? Object-oriented API?
Sunday, 16 June 2013
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- RE: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
Saturday, 15 June 2013
- Re: SDP wrapper? Object-oriented API?
- Re: Conclusion of RTCIceServer multiple-URI thread
- Re: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
- RE: SDP wrapper? Object-oriented API?
- Re: SDP wrapper? Object-oriented API?
Friday, 14 June 2013
- SDP wrapper? Object-oriented API?
- Re: How to know if a given track or media stream is being transmitted
- How to know if a given track or media stream is being transmitted
- Re: New editor's draft (v20130603)
- Re: New editor's draft (v20130603)
- Audio and Opus configurability for speed and quality (at the expense of bandwidth)
- Re: Conclusion of RTCIceServer multiple-URI thread
- Re: New editor's draft (v20130603)
Thursday, 13 June 2013
- Re: Conclusion of RTCIceServer multiple-URI thread
- Re: New editor's draft (v20130603)
- Re: quibbles about the spec
- Re: Conclusion of RTCIceServer multiple-URI thread
- Re: Draft text for identity-bound streams
- Re: Conclusion of RTCIceServer multiple-URI thread
- [Bug 22347] New: RTCIceServer should have multiple URLs
- [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 20794] i want to connect p2p with html5
- Re: Draft text for identity-bound streams
- Re: Draft text for identity-bound streams
Wednesday, 12 June 2013
- Re: Conclusion of RTCIceServer multiple-URI thread
- Re: Conclusion of RTCIceServer multiple-URI thread
- Conclusion of RTCIceServer multiple-URI thread
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Draft text for identity-bound streams
- Re: quibbles about the spec
- Anycast (Re: Allowing RTCIceServer to contain multiple URLs)
- Re: quibbles about the spec
- Re: Draft text for identity-bound streams
- Re: Draft text for identity-bound streams
- Re: Signaling without a server
- Re: Signaling without a server
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Allowing RTCIceServer to contain multiple URLs
Monday, 10 June 2013
- Re: Our simple PeerConnection example with Futures/Promises
- RE: Our simple PeerConnection example with Futures/Promises
- Re: Our simple PeerConnection example with Futures/Promises
- Re: quibbles about the spec
- RE: Our simple PeerConnection example with Futures/Promises
- Re: Our simple PeerConnection example with Futures/Promises
Sunday, 9 June 2013
- Re: Signaling without a server
- Re: Signaling without a server
- Re: Signaling without a server
- Re: Signaling without a server
- Signaling without a server
Saturday, 8 June 2013
Friday, 7 June 2013
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Allowing RTCIceServer to contain multiple URLs
- RE: quibbles about the spec
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Futures in WebRTC
- Re: Allowing RTCIceServer to contain multiple URLs
Wednesday, 5 June 2013
Friday, 7 June 2013
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Our simple PeerConnection example with Futures/Promises
Thursday, 6 June 2013
- quibbles about the spec
- Re: Allowing RTCIceServer to contain multiple URLs
- Our simple PeerConnection example with Futures/Promises
- Re: Allowing RTCIceServer to contain multiple URLs
Wednesday, 5 June 2013
- Re: New editor's draft (v20130603)
- Re: New editor's draft (v20130603)
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: Operations in invalid states: Exceptions don't make sense.
- Documents in scope for Futures discussion
Tuesday, 4 June 2013
- Re: Futures in WebRTC
- Re: New editor's draft (v20130603)
- Re: Futures in WebRTC
- Re: Futures in WebRTC
- RE: Future of Futures in Chrome
- Future of Futures in Chrome
- Re: Futures in WebRTC
- Re: Futures in WebRTC
- Re: New editor's draft (v20130603)
- Re: Operations in invalid states: Exceptions don't make sense.
- Re: New editor's draft (v20130603)
- Re: New editor's draft (v20130603)
- Re: Futures in WebRTC
- Re: New editor's draft (v20130603)
- Re: Futures in WebRTC
- Re: New editor's draft (v20130603)
- Re: New editor's draft (v20130603)
- Re: Futures in WebRTC
- Re: Futures in WebRTC
- Re: Futures in WebRTC
- Re: Operations in invalid states: Exceptions don't make sense.
Monday, 3 June 2013
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Futures in WebRTC
- Re: Futures in WebRTC
- Re: Allowing RTCIceServer to contain multiple URLs
- Re: Security of cross-origin audio
- Re: Security of cross-origin audio
- New editor's draft (v20130603)
- Details Futures teleconf
- Re: Allowing RTCIceServer to contain multiple URLs