From what I understand, this is not about cookies. It's about cookies storing information about pending server-side background tasks so the cached parts of a

From what I understand, this is not about cookies. It's about cookies storing information about pending server-side background tasks so the cached parts of a website can be sent out immediately and the slower server-side tasks can send over the results later without that resulting in a delayed response. If your slowest task takes 500ms, you simply spawn a worker who takes care of the task, immediately send out all things that are in the cache and then have your website render in <100ms. At 500ms, the rest will be filled in. It also seems to include a mechanism to figure out what resources are the most cacheable ones from the usage patterns of the clients. It's still a joke, but it's more than just setting cookies.