webrtc VS aiortc

webrtc

webrtc.rs is a port of Pion (which we also use). It's a better fit for server-side use

I want to use peer-to-peer communication and data transfer for my next side project (client-server web app). I've been doing some research and WebRTC seems to be the only option for this on the client. There are a ton of libraries and product offering for facilitating STUN/TURN servers as a service, but I'm quite interested in learning more about these protocols. That being said, I'm not the best rust programmer (part of the reason of using Rust as the server is so that I can learn more), and the signalling protocols seem rather complicated. I've looked at https://github.com/webrtc-rs/webrtc and it seems promising.

Regarding webrtc-rs. I'm a contributor to that project. The future of str0m could very well be to roll it in under that umbrella. However in these early days, I think it's better to keep str0m separate, until such time that it covers most of webrtc-rs functionality. Discussion here: https://github.com/webrtc-rs/webrtc/issues/230

This project was really fun for me is that I got to use https://webrtc.rs webrtc.rs Rust implementation of WebRTC that is based on Pion. The performance is fantastic and it is so easy to fetch + build. I had a great experience with it. It is really impressive how far the project has come!

I'm confused, you're saying as far as you can tell webrtc-rs does everything pion can do, but also saying "when the project is ready"? Can you explain what you mean? Also it seems webrtc.rs website says it's not production ready yet? How true is that?

The "Mediasoup" project provides a high level JavaScript/TypeScript interface to the WebRTC APIs. The core logic of this project is implemented in C++/Rust. Consider taking a look at the project if you want an easy-to-use library instead of the low-level libWebRTC APIs. A notable project to mention is the Pion/webrtc project which has a Golang implementation of the WebRTC API. Of course, we should mention the rust port WebRTC.rs. Let’s keep all the rustaceans happy too!

Have you considered using webrtc? It's a well-established protocol supported by all major browsers, and there's already a pure-Rust implementation you might be able to use.

If you ever did decide to add the complexity of RTC, my personal favorite SFU is MediaSoup with Janus a second. But if you want to be adventurous the Rust WebRTC project would be your go to. In any case cool project!!

Yup, WebRTC can do this. In Rust there's webrtc.rs which I've been contributing a fair amount to. Check out this example the SDP that's provided via $BROWSER_SDP and the subsequent answer that is pasted back into jsfiddle is the two way connection that /u/anlumo mentioned. With a server this is typically done with a POST request.

I'm not sure how you weren't able to find this: aiortc

You can't use Django for that, RTC is a separate protocol from HTTP. Check out https://github.com/aiortc/aiortc for a Python-based RTC stack. You write code in there which does the data processing and calls HTTP APIs or something on the Django side.

aiortc(python)

I am sure there are even more implementations that I am not aware of.

* https://github.com/pion/sctp

* https://github.com/aiortc/aiortc/blob/main/src/aiortc/rtcsct...

* https://source.chromium.org/chromium/chromium/src/+/main:thi...

* https://github.com/sctplab/usrsctp

People don't make these decisions for technical reasons only. Career wise it is a bad choice to spend your time working on pre-existing technologies. You don't become a distinguished engineer by iterating on existing technologies. You become one by being the creator of something new.

I think QUIC is great and does a good job solving the problems it was designed to solve. It is disingenuous to pretend these decisions were made only for technical reasons.

I am using aiortc. In fact, I have been experimenting with a modified version of that example: https://github.com/aiortc/aiortc/tree/main/examples/server

https://github.com/aiortc/aiortc (Python)