Server push limited to cache priming?

I've noticed that parts of the HTTP/2 spec seem to assume that priming 
the browser cache is the primary purpose of server push. However, it 
seems like server push could be used for other purposes, such as 
delivering async messages from the server to the client. I can imagine 
future application extensions that allow clients to register callbacks 
for when pushed resources arrive. This approach could be much more 
network-efficient than current long-polling techniques. Why does the 
language seem to assume that server push is only used for browser 
caching? E.g. "A server can only push responses that are cacheable". It 
seems unnecessarily restrictive.

Received on Wednesday, 19 March 2014 16:31:50 UTC