W3C home > Mailing lists > Public > www-tag@w3.org > November 2011

Re: TAG Comment on

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 15 Nov 2011 17:01:47 -0800
Message-Id: <6E3B9B96-ED36-4DA9-AA19-7BE2D9FE95D4@jumis.com>
Cc: Adam Barth <w3c@adambarth.com>, "public-webapps@w3.org" <public-webapps@w3.org>, "www-tag@w3.org" <www-tag@w3.org>
To: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>
Extend, not delete.


On Nov 15, 2011, at 3:51 PM, ashok malhotra <ashok.malhotra@oracle.com> wrote:

> But we should give it a try, no?
> The spec are still Working Drafts.
> All the best, Ashok
> 
> On 11/15/2011 2:47 PM, Adam Barth wrote:
>> These APIs are quite widely used on the web.  It seems unlikely that
>> we'll be able to delete either of them in favor of a single facility.
>> 
>> Adam
>> 
>> 
>> On Tue, Nov 15, 2011 at 2:05 PM, Noah Mendelsohn<nrm@arcanedomain.com>  wrote:
>>> This is a comment from the W3C Technical Architecture Group on the last call
>>> working draft: "Web Storage" [1].
>>> 
>>> The HTML5 Application Cache (AppCache) [2] and Local Storage [1] both
>>> provide client-side storage that can be used by Web Applications. Although
>>> the interfaces are different (AppCache has an HTML interface while Local
>>> Storage has a JavaScript API), and they do seem to have been designed with
>>> different use cases in mind, they provide somewhat related facilities: both
>>> cause persistent storage for an application to be created, accessed and
>>> managed locally at the client. If, for example, the keys in Local Storage
>>> were interpreted as URIs then Local Storage could be used to store manifest
>>> files and Web Applications could be written to look transparently for
>>> manifest files in either the AppCache or in Local Storage. One might also
>>> envision common facilities for querying the size of or releasing all of the
>>> local storage for a given application.
>>> 
>>> At the Offline Web Applications Workshop on Nov 5, 2011 [3] there was a
>>> request for a JavaScript API for AppCache and talk about coordinating
>>> AppCache and Local Storage.
>>> 
>>> The TAG believes it is important to consider more carefully the potential
>>> advantages of providing a single facility to cover the use cases, of perhaps
>>> modularizing the architecture so that some parts are shared, or if separate
>>> facilities are indeed the best design, providing common data access and
>>> manipulation APIs. If further careful analysis suggests that no such
>>> integration is practical, then, at a minimum, each specification should
>>> discuss how it is positioned with respect to the other.
>>> 
>>> Noah Mendelsohn
>>> For the: W3C Technical Architecture Group
>>> 
>>> [1] http://www.w3.org/TR/2011/WD-webstorage-20111025/
>>> [2] http://www.w3.org/TR/html5/offline.html#appcache
>>> [3] http://www.w3.org/2011/web-apps-ws/
>>> 
>>> 
> 
Received on Wednesday, 16 November 2011 01:02:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:40 GMT