W3C home > Mailing lists > Public > public-appformats@w3.org > September 2007

Re: [ ACTION-107] Updating version list identifier algorithm

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Wed, 19 Sep 2007 15:08:55 +1000
Message-ID: <b21a10670709182208x486cafb5u28178d8c89d27e0b@mail.gmail.com>
To: "Mark Baker" <distobj@acm.org>
Cc: "Ian Hickson" <ian@hixie.ch>, "Arve Bersvendsen" <arveb@opera.com>, "Arthur Barstow" <art.barstow@nokia.com>, public-appformats@w3.org 

> Stick with etags.  They work, and the tooling support is already
> pretty good.  No need to have a widget-specific mechanism when a
> generic one gets the job done.

But what if the UA does not have an etag for the resource as it was
not acquired over HTTP? For example, you gave me the widget on a CD or
sent it to me as an email attachment. Are you saying that the version
should be the etag?

Eg. config.xml:
<widget version="ImReallyAnETagdsfafddsa2" />

I'm not really following....

Kind regards,
-- 
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 19 September 2007 05:09:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:22 GMT