- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Wed, 11 Jun 2008 16:43:46 +1000
- To: "WAF WG (public)" <public-appformats@w3.org>
While working on the widgets automatic updates doc [1] (uber-draft!), I came up against a number of cache related questions: * How do we cope with HTTP code 300 (Multiple Choices): ----> multiple update description documents ----> multiple widget resources * What is the maximum number of redirects allowed? 5? * Should cookies be considered or used in automatic updates? (if so, how and what do we do with set-cookie2 and cookie2?) * Do we worry about HTTP 1.0? it does not support etags or cache-control. * Should we disallow "if-modified-since", so to allow authors to revert back to older versions of a widget? * as HTTP 1.1 allows multiple etags, should the etag attribute be a list of space delimited items or coma delimited items? or should some other delimiter be used? * do need to define how to perform an auto-update over other protocols (eg. FTP, Bit Torrent)? I'm still thinking about directives cache-control: no-cache, must-revalidate and max-age: 0, max-age, no-store, Pragma: no-cache, and how all those work in relation to GET requests in the automatic update context. I'll probably come up with more question as I continue to make my way through section 13 of RFC2616. Kind regards, Marcos [1] http://dev.w3.org/2006/waf/widgets-updates/Overview.src.html -- Marcos Caceres http://datadriven.com.au http://standardssuck.org
Received on Wednesday, 11 June 2008 06:44:35 UTC