- From: Frédéric Kayser <f.kayser@free.fr>
- Date: Tue, 22 Jan 2013 02:35:13 +0100
- To: ietf-http-wg@w3.org
Hello, is this the mechanism clients should use to stop receiving pushed resources they already have in their local cache? How are servers supposed to guess what to push or not? Is it be based on modification date, could the clients send some hints? Frédéric > 4.3.2. Client implementation > > When fetching a resource the client has 3 possibilities: > > the resource is not being pushed > > the resource is being pushed, but the data has not yet arrived > > the resource is being pushed, and the data has started to arrive > > When a SYN_STREAM and HEADERS frame which contains an Associated-To- > Stream-ID is received, the client must not issue GET requests for the > resource in the pushed stream, and instead wait for the pushed stream > to arrive. > > [...] > > To cancel individual server push streams, the client can issue a > stream error (Section 3.4.2) with error code CANCEL. Upon receipt, > the server MUST stop sending on this stream immediately (this is an > Abrupt termination).
Received on Tuesday, 22 January 2013 01:35:42 UTC