SPDY requires that the client support gzip compression of payloads.
The hope is that gzip quickly, simply and automatically gets pretty
good compression of the payload.
For more complex transformations of the HTML, CSS etc we have
Thanks for the link.
Yes, it is very similar to what I say .
In LIMI there is one disadvantage, which generates your objections.
It is called "backward compatibility".
However, if so, a new protocol that it does not already provide, no
resources are needed. So the parallel naming scheme will not be.
::>>The bundler needs to get the resources in the right order to not
delay on-paint. This sounds simple, but is surprisingly complex.The browser handles this task easily. I do not think that the server
will be more difficult.
Dynamics of course somewhat complicates the task. But the real
dynamics of either non-existent or very little.
In fact, it is a compilation of results. Static and quasi dynamics can
be cached (precompiled).
The problem with external links, by the way, we can solve by proxying
requests (for example and not in all cases).
By the way I do not propose to throw SPDY. I propose to expand it.