Implementing WebTransport and WebCodecs in an Open Source Media Server

WebTransport and WebCodecs are new API's that provide powerful, low-level contolsover the RTC stack but developers must implement many features of WebRTC themselves. Intel will discuss the benefits and disadvantages of these technologies and their implementation learnings from using these API's in the open source Open WebRTC Toolkit (OWT) media server project.
Speaker:
Jianjun Zhu, Software Engineer, Intel
Thank you to our sponsors!
Google - webrtc.org
Agora - www.agora.io
Daily - www.daily.co/
Dolby - bit.ly/3vgy7qy
Element - ems.element.io/
Intel - bit.ly/31AtHRy
RingCentral - developers.ringcentral.com/
SUBSCRIBE TO OUR WEEKLY: webrtcweekly.com/
00:00 - Intro
02:37 - WebTransport & WebCodecs
06:07 - Client pipeline
10:42 - Server-side stack
11:22 - Optimization and status
13:12 - Demo

[@jeffg4686]

Anyone know if webtransport has same "DataChannel" feature as webrtc, which (I believe) was for 'raw data' (not A/V)?

[@btwiuse]

WebRTC data channels support peer-to-peer communications, but WebTransport only supports client-server connection.

[@jeffg4686]

@@btwiuse - thanks, I found some stuff indicating that maybe RTCQuicTransport is the new method (p2p over quic)

[@davidbrenchley]

Would you be able to record the incoming media on the server?

[@KrankyGeek]

The OWT server does have some options for recording.

[@jluflyingzl]

cool