wtransport

wtransport copied to clipboard

Updates the requirements on [quinn](https://github.com/quinn-rs/quinn) to permit the latest version. Commits 0e9a196 Rename UnknownStream to ClosedStream for clarity 130d956 Don't treat UnknownStream as an error in SendStream::stopped b42e21e Make SendStream::finish...

dependabot[bot]

The stream error codes are modelled incorrectly. Currently, `wtransport` just passes the error code numeric value (in fact, the same `VarInt`) through to the QUIC / HTTP3 layer. However, this...

MOZGIII

Make receive_datagram return BytesMut

3

Some use cases, such as using datagrams with serde via `tokio_serde::Framed`, require that messages received from the peer are `BytesMut` instead of `Bytes`. Currently, `Connection::receive_datagram()` returns a `Datagram` which itself...

TheButlah

looping over RecvStream::read causes an infinite loop without the client sending anything.

10

i have the following server code that loops over received message on RecvStream::read : ```rs use wtransport::Endpoint; use wtransport::Identity; use wtransport::ServerConfig; #[tokio::main] async fn main() { let config = ServerConfig::builder()...

JimitSoni18

Is it possible to use this library for client-server communication with Android and iOS devices, avoiding deep dives into native HTTP APIs? **Possible Solution:** Exploring shared libraries (e.g., [Mozilla UniFFI](https://github.com/mozilla/uniffi-rs))...

yalihart

In WTransport, `SendStream::stopped` is defined as `stopped(self)` while Quinn defined it as `stopped(&mut self)`. I think it can be safely changed to `&mut self`.

kyori19

Is there a reason to have separate client and server endpoints?

4

I feel like I am missing something, but I don't see a reason why there is a need to have incompatible types for the endpoints. With QUIC in general and...

MOZGIII

The `with_server_certificate_hashes` on the *client* should not be under a feature flag

5

The rationale is simple: for the client, the use of the server certificate hashes is not dangerous, and they are **definitely not necessarily self-signed**. It is very much expected for...

MOZGIII

Firefox support

4

Hi, I was wondering if there were any caveats/special handling that is needed for Firefox support. I've had an issue where WebTransport connections get rejected on Firefox. It doesn't seem...

cBournhonesque

Access to low-level quinn details in client

3

I need to set quinn transport congestion control to BBR, but there's no way to do it currently. It would be great to have a lower level access there, maybe...

MOZGIII