- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Wed, 28 May 2008 21:28:12 +1000
- To: "Arve Bersvendsen" <arveb@opera.com>
- Cc: "Thomas Roessler" <tlr@w3.org>, "WAF WG (public)" <public-appformats@w3.org>
On Wed, May 28, 2008 at 7:25 PM, Arve Bersvendsen <arveb@opera.com> wrote: > On Wed, 28 May 2008 11:10:56 +0200, Thomas Roessler <tlr@w3.org> wrote: > >>> 2. Point to an XML file written in our custom XML format (described >>> below). >> >> I'd drop that. > > While more complicated, it buys a number of freedoms: > > 1. In the case that any security-related settings for the widget changes, > they can be reviewed automatically, or optionally manually by the user, and > download of an updated resource can be prevented if the updated version is > not acceptable. This is particularily important on slow connections, since > some widgets run into the megabyte range I might just add that another use case for the XML update format is for dynamically generated widget resources, where it may not be possible (or make sense) to use caching mechanisms. -- Marcos Caceres http://datadriven.com.au
Received on Wednesday, 28 May 2008 11:28:54 UTC