Hi,
Almost all web developer I know use externally linked CSS resource in their
web projects. That means that the browser needs to (1) request the html
page (2) parse the html (3) request for the CSS resource that is linked
from the html document. The problem with externally linked resources is
On Thu, Mar 13, 2014 at 6:57 AM, Tingan Ho tinga...@gmail.com wrote:
Thought and feedback is welcomed
Surely it would be better to send an archive file containing the
resources the server expects the client to need, employing the Accept
header to decide whether to do so (ie, in order to request
(Ideally, by the way, we would bake cache expiration and any other
relevant response header metadata into the archive format. Of course,
this puts the onus on the browser to decide whether to send a separate
request for a particular resource in case it has changed, not on the
server to know
