It may be a little too soon to bring this up, but I wanted to raise awareness for this interesting specification that http responses may soon be a bundle of responses.
In the future, we may also see alternate distribution mechanisms for http resources based on the signed-response specification. An example use case: John has a signed, bundled instance of a page, he could give it to Mark who can then unbundle the resource, check the signatures, & browse the website, even though both may be offline.
My feeling is that hx-uri could be adapted to handle bundled exchanges & the subresources they entail. If alternate http resource transports do emerge, as the previous paragraph discusses, it's hard to guess whether there's a sensible manner in which hx-uri might apply.
The Bundled HTTP Exchanges draft allows for a http server to respond with a CBOR encoded bundle comprising multiple http responses.
Chrome filed an intent to implement for this capability ~2 months ago.
There was just an IAB Exploring Synergy between Content Aggregation and the Publisher Ecosystem/ESCAPE Workshop that in part discussed signed & bundled exchanges, collectively known as Web Packaging.
It may be a little too soon to bring this up, but I wanted to raise awareness for this interesting specification that http responses may soon be a bundle of responses.
In the future, we may also see alternate distribution mechanisms for http resources based on the signed-response specification. An example use case: John has a signed, bundled instance of a page, he could give it to Mark who can then unbundle the resource, check the signatures, & browse the website, even though both may be offline.
My feeling is that hx-uri could be adapted to handle bundled exchanges & the subresources they entail. If alternate http resource transports do emerge, as the previous paragraph discusses, it's hard to guess whether there's a sensible manner in which hx-uri might apply.