💾 Archived View for gemi.dev › gemini-mailing-list › 000918.gmi captured on 2023-12-28 at 15:55:01. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
The QUIC transport protocol, which may replace TCP for a lot of usages, specially HTTP, is now a standard: https://www.rfc-editor.org/info/rfc9000 QUIC is very much designed for the Web, with its special requirments, such as parallel downloading of several resources. Gemini, being simpler, may be less interested and may stay with TCP. Although the lower latency of QUIC, partly due to the merge with TLS, may be interesting since Gemini always uses TLS.
On Fri, May 28, 2021 at 10:16:55AM +0200, Stephane Bortzmeyer wrote: > The QUIC transport protocol, which may replace TCP for a lot of > usages, specially HTTP, is now a standard: > > https://www.rfc-editor.org/info/rfc9000 > > QUIC is very much designed for the Web, with its special requirments, > such as parallel downloading of several resources. Gemini, being > simpler, may be less interested and may stay with TCP. Although the > lower latency of QUIC, partly due to the merge with TLS, may be > interesting since Gemini always uses TLS. >From my previous understanding of QUIC, there's no good kernel/libc support, so it imposes a much higher minimum client/server size on a Gemini implemntation. We can assume a TLS library will be present everywhere, QUIC not so much. Maybe once the web browser titans have beaten down that door we can revisit. Part of the joy of Gemini is that you don't need a ton of libraries to do it right, and I'd like to keep that.
---
Previous Thread: [ANN] GemThread: an experimental conversation server