- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 10 Dec 2009 15:31:42 +0000 (UTC)
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Dan Connolly <connolly@w3.org>, www-archive@w3.org
On Thu, 10 Dec 2009, Julian Reschke wrote: > Ian Hickson wrote: > > On Thu, 10 Dec 2009, Dan Connolly wrote: > > > But I get the impression that the HTML 5 spec discusses caching, > > > expiry/time-to-live, refreshing pages, messages to worker threads, and > > > that sort of thing, yes? In that case, I don't think you can use this > > > time-flattened worldview. > > > > I don't see why not... even with caching, it's still the bits that have > > times-to-live and are cached, etc; similarly with refreshing, and messages > > across Windows, etc -- it's always in terms of concrete resources, not > > anything abstract. > > It's in terms of responses (entities), which include a bag-of-bits (the body), > plus metadata (where the metadata is not only caching information, right?). In HTML5, which I believe is what Dan was referring to, it's in terms of resources and the resource's metadata. Notice how there's no need to refer to the HTTP concept of "resource" for this. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 10 December 2009 15:32:19 UTC