aioquic

Going a bit further, it seems like there's a grain of truth here, HTTP/2 has a stream priority dependency mechanism [1] and this report [2] from Imperva describes an actual Dependency Cycle DoS in the nghttp implementation. Unfortunately that's where it seems to end... I'm not that familiar with QUIC and HTTP/2, but I think the closest it gets is that the GitHub repo exists and has a `class QuicConnection` [3]. Beyond that, the QUIC protocol layer doesn't have any concept of exchanging stream priorities [4] and HTTP/2 priorities are something the client sends, not the server? The PoC also mentions HTTP/3 and PRIORITY_UPDATE frames, but those are from the newer RFC 9218 [5] and lack the stream dependencies used in HTTP/2 PRIORITY frames. I should learn more about HTTP/3! [1] https://blog.cloudflare.com/adopting-a-new-approach-to-http-... [

> whole point of a library like requests is to make networking requests. The whole point of requests is to make HTTP requests easy. HTTPLib was/is an arse to use. as HTTP3 is really not that widely adopted, and where it is, has fallbacks to 1.1 whats the point? Plus the people who are keen on HTTP3 also seem to be keen on async, https://github.com/aiortc/aioquic/tree/main/examples which even though it isn't seems to be overly complex and difficult to use. Contrast that to r.get(url)....

One of the interesting patterns happening in Rust is io-less libraries. I'm not sure where best to link this phenomenon. It here s a open issue for an io-less quic library, from 2019, https://github.com/aiortc/aioquic/issues/4 It'd be so fracking sweet to see filesystems follow this pattern. If we could re-use the file system logic, but apply it to windows or fuse or Linux or wasm linearly-addressed-storage, that would allow such intensely cool forms of portability/reuse & bending/hacking.

Yes, I'm quite sure this works this way. I was looking into a few implementations and the specs: https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-ov... https://www.w3.org/TR/webtransport/ https://github.com/w3c/webtransport https://github.com/w3c/webtransport/blob/main/explainer.md https://github.com/aiortc/aioquic/blob/main/examples/http3_s... WebTransport just landed in Firefox release versions and is available since some time in Chromium so it's indeed ready for hacking! :-D

Given that the majority of people uses the web through very often quite crappy mobile links HTTP/3 is actually a significant win from the user experience perspective. It can be all the difference between "site is completely unusable" and "site is slow, but you get through". Of course it's true that QUIC is a complexity monster. OTOH HTTP/3 is actually quite simple when you have the QUIC layer implemented. A simple HTTP/3 server is no more than this: https://github.com/aiortc/aioquic/blob/main/examples/http3_s...

for those wishing to use http3 with a Python web framework, the ASGI hypercorn[1] currently supports it. made a Django example last week with a sample client based on the examples from aioquic[2]: https://github.com/djstein/django-http3-example this example also includes the first pass at async Django REST Framework using adrf[3] based on these GitHub issues: - https://github.com/encode/django-rest-framework/pull/8617 - https://github.com/encode/django-rest-framework/issues/8496 sources [1]: https://github.com/pgjones/hypercorn [2]: https://github.com/aiortc/aioquic [2]: https://github.com/em1208/adrf

For HTTP/3 support with python clients: - aioquic supports HTTP/3 only now https://github.com/aiortc/aioquic - httpx is mostly requests-compatible, supports client-side caching, and HTTP/1.1 & HTTP/2, and here's the issue for HTTP/3 support: https://github.com/encode/httpx/issues/275

That sounds like you need better software then :) Realistically what do you think the timelines are for QUIC? When Bernard published the QuicTransport stuff I tried a few different versions and it only worked aioquic[0] (which is a really fantastic implementation)! But with 29 drafts and most servers not supporting them all feels like we still have some time to go. So QUIC as a server is much less likely to happen then ICE/DTLS/SCTP which have implementations that work everywhere. [0] https://github.com/aiortc/aioquic