3 ms·

We really, REALLY need a "standard" QUIC API, this thing is getting out of hand IMHO.

• littlecranky67 3y ago
  This was called for. QUIC is UDP based, and shifts the burden of implementing stuff like congestion control into userspace. There are already plenty different congestion control algorithms in the (linux-)kernel for TCP so you can expect a myriad of different implementations (and configurations) in QUIC - but this time on a per-program level.
  • qalmakka 3y ago
    I do understand that, but I'd still like a "common" basic API for those people that just want to transmit data efficiently from point A to point B. If QUIC is harder than TCP, people will just stick to that instead of switching to QUIC. I don't say we need a SOCKET_QUIC, but it would be nice to have at least a way to open a connection that's similar on every library.
  • ta8903 3y ago
    Ah yes, the waylandification of a protocol.