shanebellone

Would you pay for a service that reduced the HTTP requests produced by your multimedia?

This process results in faster load times.

I'm interested in tech R&D.

Please share your story about selling or licensing intellectual property (in this case code-based IP). Was it a net positive? Would you do something differently if you had the chance?

Thanks (in advance) for sharing.

Is there an existing solution that retrieves n-images with a single request? Rather than an individual request for each image?

Note: I am familiar with HTTP2 multiplexing.

Streaming data would allow for "browser-based applications" (e.g. single request/refresh-less web applications).

Why is the standard approach still transactional?

Afternoon HN,

I may have rather serendipitously implemented HTTP/3 support for a Flask-like CMS.

Does HTTP/3 reduce server requests by concatenating multi-resource requests into a single request conveyed through a "chained-path"?

For example:

Loading example.com/about requires loading style.css and favicon.ico.

HTTP/2 would request example.com/about, request style.css, request favicon.ico.

Does HTTP/3: request example.com/about & style.css & favicon.ico with a single request path similar to "/about/style.css/favicon.png"?

Any insight would be appreciated. Thanks!