W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Reference set in HPACK

From: Roberto Peon <grmocg@gmail.com>
Date: Wed, 2 Jul 2014 18:16:37 -0700
Message-ID: <CAP+FsNcrD0pe=OmrFdk7BebdNjqs28=0LNfqHwxL77NN+UCwCw@mail.gmail.com>
To: "Eric J. Bowman" <eric@bisonsystems.net>
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Kazu Yamamoto <kazu@iij.ad.jp>, HTTP Working Group <ietf-http-wg@w3.org>
You can cache an object that has inlined resources within it, but you
cannot cache those resources separately.
You can't cache a resource that doesn't have a name.

-=R


On Wed, Jul 2, 2014 at 5:54 PM, Eric J. Bowman <eric@bisonsystems.net>
wrote:

> Roberto Peon wrote:
> >
> > Inlining is the technique most often used to reduce the number of
> > request.
> >
>
> I've also always considered it a worthwhile technique for byte-shaving,
> as combining lots of small images into one mosaic image eliminates
> whatever redundant bytes are inherent to the chosen image format.
>
> >
> > It is a strategy that works well most of the time for cold
> > pageloads, but it also harms latency for subsequent navigations
> > deeper into the site as those resources cannot be cached.
> >
>
> But you lost me there, as I've never had a problem caching those
> resources? Or does "inlining" not mean what I think it means?
>
> -Eric
>
Received on Thursday, 3 July 2014 01:17:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC