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

idea -- MAX_PUSH_RESOURCE_SIZE

From: Peter Lepeska <bizzbyster@gmail.com>
Date: Mon, 4 Nov 2013 10:00:05 -0800
Message-ID: <CANmPAYH2t3KCdUMXSin9kOHJmDV5nNq033intpg1OetHcr3tnQ@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
If the client determines, for any reason, that it does not wish to
   receive the pushed resource from the server, or if the server takes
   too long to begin sending the promised resource, the client can send
   an RST_STREAM frame, using either the CANCEL or REFUSED_STREAM codes,
   and referencing the pushed stream's identifier.

   A client can use the SETTINGS_MAX_CONCURRENT_STREAMS setting to limit
   the number of resources that can be concurrently pushed by a server.
   Advertising a SETTINGS_MAX_CONCURRENT_STREAMS value of zero disables
   server push by preventing the server from creating the necessary
   streams.  This does not prohibit a server from sending PUSH_PROMISE
   frames; clients need to reset any promised streams that are not
   wanted.


As per above, the browser currently can only set max concurrent
streams to limit the amount of data pushed to it but perhaps better is
to set a max size of file that the browser is willing to accept via
server push. That way a browser can adjust the amount of data pushed
to it depending on its available cache space. So, for instance, a
browser on a small device would set MAX_PUSH_RESOURCE_SIZE setting to
a value lower than a browser on a PC with lots of storage.


Thanks,


Peter
Received on Monday, 4 November 2013 18:00:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:19 UTC