quinn VS webrtc

Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.

Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.

> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.

Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.

Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.

Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.

[1]: https://github.com/quinn-rs/quinn

quicssh-rs is quicssh rust implementation. It is based on quinn and tokio

Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!

By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.

QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.

Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn

You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .

Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

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

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

I am trying to get WebRTC working using Rust https://github.com/webrtc-rs/webrtc

I have opened an issue on GitHub [1], we can continue there.

[1] https://github.com/webrtc-rs/webrtc/issues/426

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.