W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt)

From: Frédéric Kayser <f.kayser@free.fr>
Date: Tue, 22 Jan 2013 09:19:39 +0100
Message-Id: <760C0C47-68E1-4811-AC76-0495713A8823@free.fr>
To: ietf-http-wg@w3.org
Ok,
I'm familiar with the data URI scheme used by front-end developers. Since "push" is way closer to the server it will probably require the creation of "pushing rules" (if this HTML page is requested push this CSS file and these background images along) or is it envisioned that the server could parse HTML/CSS files to automatically pick up other resources to push, or even train some kind of IA to learn which file request is usually followed by other requests and anticipate such patterns?

Frédéric

Le 22 janv. 2013 à 03:23, William Chan (陈智昌) a écrit :

> Note that web developers are already pushing resources. It's called
> resource inlining
> (https://developers.google.com/speed/docs/pss/InlineSmallResources).
> These resources do not have their own URLs, are usually inlined into
> uncacheable documents, and thus are rarely cached at all. Using server
> push will enable them to have their own URLs and be cached by the
> client if that makes sense.
> 
> Remember, once you issue a request to a server, the server can send
> you anything in return. It's in our interest to provide them better
> facilities for sending responses, or they will hack around it in less
> optimal ways.
Received on Tuesday, 22 January 2013 08:20:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 January 2013 08:20:08 GMT