Cameron Bytheway
Cameron Bytheway
Are you wanting to use `s2n-tls` or `rustls`? If you're using `rustls` then it shouldn't be building `s2n-tls` at all. Is that `identity-manager` crate also depending on `s2n-quic`? (as a...
This should be supported on the server by implementing the client hello callback. In that callback, you would associate whatever `Config` object with each connection as it comes in. On...
If we're concerned about integration tests, we can pass `test --lib` by default, which will only build the unit tests (see https://doc.rust-lang.org/cargo/commands/cargo-test.html#target-selection). You could then make integration tests opt in...
The current Quinn implementation doesn't actually send the data on the stream; it just buffers it until a `poll_ready` is called again. So that would need to change as well....
Like mentioned in the issue, it would be most obvious to behave like the [Sink](https://docs.rs/futures/latest/futures/sink/trait.Sink.html#tymethod.poll_ready) trait: `poll_ready` > This method must be called and return Poll::Ready(Ok(())) prior to each call...
Yeah AsyncWrite isn't the most efficient way of transferring data, especially when the data is already a `Bytes`. With [s2n-quic](https://docs.rs/s2n-quic/latest/s2n_quic/stream/struct.SendStream.html) we've exported poll functions for all of the stream operations....
we _just_ launched yesterday :smile:
We had to ignore a few test cases in s2n-quic, so it's doable: https://github.com/aws/s2n-quic/blob/dce3fd056f9a263d6fd97de932c9864d73a7e92f/.github/workflows/qns.yml#L556
Another option would be to rename the methods to something like `set_data` and `poll_send_data`, which it seems like is how it's being used currently. But if we're considering an API...
Not necessarily. If the caller used `copy_to_bytes` with `chunk` lengths the `Buf` impl would specialize on it: ```rust let len = buf.chunk().len(); let bytes = buf.copy_to_bytes(len); ``` (see, for example,...