Combining it with dynamically generated DNS names might be a nice "content accelerator" add-on for CDNs, etc.
ie: a page uses resources, each of which has a unique url.
You have custom infrastructure (that sits in front of a normal website) which dynamically generates a new subdomain for each resource, and replaces the resource urls with the new urls (using the subdomain).
At the top of the page (or ideally on the previous page) you include some zero-length resources with the same MIME-type as the resources you want to serve.
The browser requests these resources, and as soon as you have the connection open you reply with the zero length resource and then the actual resource you want to serve.
Subsequently the browser requests the actual resource, and finds it already waiting.
The unique hostnames are needed to allow you predict which resource will be requested.
(This was probably patentable until I wrote it all out, too ;))
Combining it with dynamically generated DNS names might be a nice "content accelerator" add-on for CDNs, etc.
ie: a page uses resources, each of which has a unique url.
You have custom infrastructure (that sits in front of a normal website) which dynamically generates a new subdomain for each resource, and replaces the resource urls with the new urls (using the subdomain).
At the top of the page (or ideally on the previous page) you include some zero-length resources with the same MIME-type as the resources you want to serve.
The browser requests these resources, and as soon as you have the connection open you reply with the zero length resource and then the actual resource you want to serve.
Subsequently the browser requests the actual resource, and finds it already waiting.
The unique hostnames are needed to allow you predict which resource will be requested.
(This was probably patentable until I wrote it all out, too ;))