samples VS aioquic

Why do you need an ordinary HTTP Web server when you have HTTP/3 and QUIC support in WebTransport (https://www.w3.org/TR/webtransport/; https://github.com/GoogleChrome/samples/tree/gh-pages/webtransport)?

Web Payment Request Examples by Google

This code sample is an enhancement on top of Service Worker Mock. Service Worker Mock explains how to write unit tests for service works. Since it is not maintained any more, I am writing this code sample to unblock ourselves from the current issues in that library. Tests are written using the sample service worker given at service worker example

It's definitely possible to get this up and running in 1-2 months using like Flutter. An other option is to use Web Bluetooth if you feel more comfortable doing web stuff instead, here are many samples https://github.com/GoogleChrome/samples/tree/gh-pages/web-bluetooth

Technically WebTransport https://github.com/GoogleChrome/samples/tree/gh-pages/webtransport provides a means to run code (using aioquic in Python) on local machine requested from any site where CSP does not block the request.

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.

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 adrift[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

In your estimation where does the QUIC specification, HTTP/3 specification, WebTransport specification, aioquic QUIC and HTTP/3 implementation in Python https://github.com/aiortc/aioquic (notice the GoogleChrome/samples WebTransport sample code is described as local server "There's code for a sample local server at https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py") fit into the categories you color "Framework" and "Webserver"?

Whilst the article rightly mentions aioquic to use HTTP/3 with Python, it is only a minimal example server. Hypercorn is a compete ASGI server built on aioquic that is likely more useful practically.