- From: Mark Baker <distobj@acm.org>
- Date: Tue, 18 Sep 2007 22:30:34 -0400
- To: "Marcos Caceres" <marcosscaceres@gmail.com>
- Cc: "Ian Hickson" <ian@hixie.ch>, "Arve Bersvendsen" <arveb@opera.com>, "Arthur Barstow" <art.barstow@nokia.com>, public-appformats@w3.org
On 9/18/07, Marcos Caceres <marcosscaceres@gmail.com> wrote: > > In any case, I would recommend not parsing versons at all. Just treat them > > as opaque strings, and assume that there is an upgrade if the version on > > the server doesn't match the version in the client. > > I could live with this, but it still makes me uncomfortable. What > happens if I accidentally override a new version with an old version > by mistake and don't realize it for a few days? Don't do that! What happens if you mislabel 1.7 as 1.6? 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. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
Received on Wednesday, 19 September 2007 02:30:39 UTC