docs/question: differences & pros & cons as compared to wtransport?

[jessekrubin]

Hi!

I am adding web-transport to a server I am working on and am curious what the differences between this repo/set-of-crates and the wtransport crates (https://github.com/BiagioFesta/wtransport)

I think some sort of comparison would be good; I think it maybe makes more sense for some sort of comparison to live in this repo as it is (AFAICT) the newer set of crates?

Thanks so much! Works great!

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Add COMPARISON.md (275-line detailed side-by-side comparison of web-transport vs wtransport: quick summary table, architecture, API examples, cross-platform support, protocol details, performance, maturity, and recommendation favoring web-transport for browser use) and update README.md to include a reference link to the new comparison.

• Add a new COMPARISON.md with a comprehensive side-by-side comparison of web-transport vs wtransport (architecture, API, platform support, protocol/implementation depth, use cases, migration, performance, examples, references, and contributing) and update README.md to add a "Comparison with wtransport" section linking to COMPARISON.md.

• ✅ Create PR with these edits
• 📋 Get copyable edits

[kixelated]

Hey @jessekrubin , both crates were made independently around the same time. I renamed from webtransport-quinn to web-transport-quinn because webtransport wasn't available but web-transport was

TBH I don't know the differences, except that I copied the Quinn API verbatim on purpose.

[jessekrubin]

Howdy @kixelated!

Thanks so much for the honest response! AFAICT the deps for thing I am working on now align more with your libraries so I am going to give it a go. Can keep you posted if you like.

Different question: Do you have any recs w/ respect to integrating w/ an axum server? I figure worst case scenario I can just have 2 server tasks.

[kixelated]

Howdy @kixelated!

Thanks so much for the honest response! AFAICT the deps for thing I am working on now align more with your libraries so I am going to give it a go. Can keep you posted if you like.

Different question: Do you have any recs w/ respect to integrating w/ an axum server? I figure worst case scenario I can just have 2 server tasks.

I don't know the state of HTTP/3 servers. The problem is that they would need to support WebTransport natively because it happens via a HTTP/3 handshake.

But you can always host Axum via TCP and WebTransport via UDP on the same port. That's what I'm doing for moq-relay. Also here's how I'm supporting the web-transport-ws fallback via Axum.

[jessekrubin]

@kixelated thanks so much that is super super helpful!

[jessekrubin]

@kixelated thanks so much for this impl!

I am working with it pretty regularly.

I dont know how familiar you are with python but I am considering adding bindings for your lib(s) (particularly the quinn based impl) to my side project as a means of testing my current wt-server-project (https://github.com/jessekrubin/ry -- wraps a bunch of rust crates). I was wondering if you would want to talk about what you think that would look like or have any recommendations. lmk if you want to talk!

[kixelated]

I haven't used Python enough to provide much of an opinion, but that's cool.

[jessekrubin]

@kixelated Will keep you posted if I have the time to do some sort of wt-python bindings.

Can I keep asking you questions here?

I read your wt-quiche readme and was curious what you have to say about quiche vs quinn. Does one out perform the other? what are the pros/cons of each? I have been getting strange connection issues occasionally with quinn.

[kixelated]

I read your wt-quiche readme and was curious what you have to say about quiche vs quinn. Does one out perform the other? what are the pros/cons of each? I have been getting strange connection issues occasionally with quinn.

Quinn is simpler and works great. Quiche is complex but better suited for production.

web-transport-quiche is trying to bridge the gap between the two. The Quinn API but the Quiche backend. However, it still has some bugs, so I wouldn't recommend it just yet.

[jessekrubin]

Interesting. I tested it out with a frame-buf server I am working on and the throughput was much higher.

[kixelated]

Interesting. I tested it out with a frame-buf server I am working on and the throughput was much higher.

Yeah there's probably some subtle wakeup bug. Maybe I can have codex churn on it a bit.

[jessekrubin]

Looks like youre based in SF? I am in oakland if you wanna meet up sometime to shoot the shit

[jessekrubin]

Have you looked at s2n-quic?

[kixelated]

Looks like youre based in SF? I am in oakland if you wanna meet up sometime to shoot the shit

El Cerrito actually, so even closer. There's a Rust meetup soon if you're interested: https://luma.com/cyu67mpz?tk=c7YCWA

Have you looked at s2n-quic?

Not really, I know the Cloudflare guys so I'm biased.