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

Re: ID for Immutable

From: Alex Rousskov <rousskov@measurement-factory.com>
Date: Fri, 28 Oct 2016 09:23:54 -0600
To: HTTP working group mailing list <ietf-http-wg@w3.org>
Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Message-ID: <2eaa785f-8736-f677-db11-7595fae3eb9a@measurement-factory.com>
On 10/28/2016 08:44 AM, Kari Hurtta wrote:
> If server can't calculate hash-function over resource,
> is is really static non-caching resource?

There is sometimes a big difference between the _ability_ to calculate a
hash and the _expense_ of doing so. AFAICT, immutable responses may
still be dynamically generated (or otherwise costly to produce) on the
origin server.

For example, loading, encoding, and hashing a 2-hour video of the 1948
Olympics opening ceremony could be rather expensive, but will produce
the same immutable result [until the server has to inject a fresh set of
advertisements sometime tomorrow].

Received on Friday, 28 October 2016 15:24:36 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 October 2016 15:24:38 UTC