public-webrtc@w3.org from July 2013 by subject

[Bug 20819] no priority API

[Bug 22428] Please unify the WebSocket and RTCDataChannel "readyState". enum RTCDataChannelState { "connecting", "open", "closing", "closed" }; VS const unsigned short CONNECTING = 0 [...]

[rtcweb] e= lines (Re: Summary of Application Developers' opinions ..)

[rtcweb] Locus of API discussion

[rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

[rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

[rtcweb] SDP is not suitable for WebRTC

[rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

[rtcweb] Unified plan IPR

[SPAM] RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers

a new API proposal

A view on the current webRTC API and next step...

API design

Audio and Opus configurability for speed and quality (at the expense of bandwidth)

Be vewy, vewy qwiet...

Cisco's position on the WebRTC API

Cross posting: Re: [rtcweb] SDP is not suitable for WebRTC

Discussing new API proposals

do we want success and failure callbacks on addStream?

DOM Futures

DOM Futures (was: Mediastream Recording implementation)

Expose capabilities / Allow for IP:Post based connections / Better abstraction

Fwd: [rtcweb] e= lines (Re: Summary of Application Developers' opinions ..)

Google's position on the WebRTC API

Improve error message when browser denies access to getUserMedia()

IPR related to draft-roach-mmusic-unified-plan-00

JavaScript API on top of SDP

Locus of API discussion

Membership of this WG (Re: [rtcweb] Summary of Application Developers)

Moving forward with SDP control

muting/hold (was Re: Cisco's position on the WebRTC API)

On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

Pause / resume

Proposal: Different specifications for different target audiences

Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

Recap from WebRTC World

SDP is not suitable for WebRTC

SDP wrapper? Object-oriented API?

sdpMLineIndex required in RTCIceCandidate?

server-centric vs. P2P (was Re: Proposal: Different specifications for different target audiences)

setting bandwidth

Teleco Integrators vs Web Developers vs Browser Implementers

The best API possible (Was: Teleco Integrators vs Web Developers vs Browser Implementers)

TPAC Registration open

Trickle ICE questions?

Unified plan IPR

URL.createObjectURL() for DataChannels

VS: [rtcweb] SDP is not suitable for WebRTC

VS: Teleco Integrators vs Web Developers vs Browser Implementers

VS: VS: Teleco Integrators vs Web Developers vs Browser Implementers

WebRTC Java Applet

WebRTC Web APIs for On-board Multimedia Devices Handling and Control

Why people munge SDP

XSF Jingle Special Interest Group.

Last message date: Wednesday, 31 July 2013 23:22:18 UTC