WebRTC changes in Chrome Canary / Dev Channel
The Chrome WebRTC package has changed this week for user of Chrome Canary and Dev channels. We thought it would be a good idea to drop a note on the blog as we have not yet caught up with updating our own documentation. The Chrome implementation of the WebRTC API is now a closer match to current W3C WebRTC API draft. It includes the ability for separate audio / video sessions. (ref: Stream API)
SRTP (encryption) now on by default, meaning all audio and video data will be encrypted. This will maybe break a few early phone interop demos.
Hints on how to migrate your early prototypes can be found in this changelist.