Comments (11)
I am not a QUIC expert, but from my understanding it is not a replacement for WebRTC. There is a proposed protocol to use QUIC with WebRTC, but that's specific to multiplexing QUIC with other types of WebRTC. Rather than replace WebRTC, QUIC would act as the means of transit for certain types of data alongside WebRTC. Abstractly speaking, it seems that something like QUIC could eventually be used for a wholesale replacement for the transport layer in WebRTC, but I think it'd need better primitives for unreliable data. There are some proposals for that, but they are not adopted.
Again, I am not deeply knowledgeable of QUIC and it's current direction with respect to WebRTC, but I believe it's not quite right to think of it as a replacement, and too soon to think of it as a full-scale transit layer substitute. I would speculate that it would be interesting to eventually try to integrate the QUIC-extensions proposed to WebRTC for this project, but it may be premature to do so: both QUIC itself and the WebRTC integration for it have not been finalized.
from webrtc.
Google's messaging platform for text and video is 100% based on QUIC.
YouTube is all QUIC.
40% of all internet mobile traffic is UDP. Mostly because of YouTube and Netflix apparently.
So yes it replaces the transport channel.
It's UDP with the TCP congestion control backend in.
So if you want video conferencing then you just transcode and stream onto this transport.
It's exactly what you do with data except it's video frames.
Use whatever codec you want.
Am just saying that it can easily replace QUIC and be careful because allot of the opinions are biased due to the webrtc versus Google versus Microsoft war over this standard.
I see QUIC as a huge opportuniy to break out of this decades old webrtc legacy code. It's horrible stuff down in the weeds.
from webrtc.
Almost forgot this gem !!?
go-libp2p-quic-transport
from webrtc.
https://github.com/libp2p/go-libp2p-quic-transport
from webrtc.
@gedw99 thanks for sharing this stuff! I know nothing about QUIC, but will do a deep dive this weekend :)
from webrtc.
from webrtc.
It's going through standards WG at the moment
from webrtc.
https://github.com/libp2p/go-libp2p-quic-transport
Probably the best example of the usefulness and practicality of QUIC.
You can see the multiplexing aspects in the code and issues
from webrtc.
https://github.com/libp2p/go-libp2p-quic-transport
Probably the best example of the usefulness and practicality of QUIC.
Unfortunately no example code though. But you can backtrack the to the original author to see examples using cli
You can see the multiplexing aspects in the code and issues
from webrtc.
Added to roadmap! I think it would be great if we could play with this in pion-WebRTC. Hopefully we can get to a point where it is easier to prototype things here then other implementations of WebRTC.
from webrtc.
Hey @Sean-Der
thanks for adding https://github.com/pion/quic
from webrtc.
Related Issues (20)
- Sending RTCP Reports as RFC8888 via PeerConnection HOT 1
- Ability to configure ice candidates gathering timeouts
- PeerConnection should drop reference to datachannel when it's closed
- Trickle ICE not working properly HOT 1
- OnTrack will not be fired HOT 10
- Pion cannot connect with Janus without manually specifying Candidates SDPMid
- Improve pluggability and testability across pion modules though Interfaces HOT 1
- Single Port mode second connect failed HOT 3
- rtp-to-webrtc H264 via gstreamer issue HOT 4
- Sending two separate video streams with rtp-to-webrtc under two different ports HOT 1
- data-channels-detach-create example is missing HOT 1
- Is there any example where the original h264 data can be sent to pion directly at the interface layer? HOT 2
- Go version in mod file too low for webrtc v3 HOT 5
- Generate host candidates with component 1 only when a=rtcp-mux is present HOT 6
- Goroutine leaks when using datachannel with a multi mux with single port HOT 3
- SampleBuilder causes segmentation fault HOT 5
- Ontrack is never be fired on client side neither with pion OnNegotiationNeeded HOT 1
- Test Coverage for Receiving RTXs HOT 1
- Specific port to automatically open? HOT 1
- How do I make Multicasting by one-to-many transmissions HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webrtc.