W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: TAG Comment on

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Fri, 18 Nov 2011 10:44:18 -0500
Message-ID: <4EC67D52.2090800@arcanedomain.com>
To: Arthur Barstow <art.barstow@nokia.com>
CC: public-webapps@w3.org, "www-tag@w3.org" <www-tag@w3.org>
 > Noah - the TAG's comment has been added to the comment tracking document
 > for this LC:
 >
 > http://www.w3.org/2008/webapps/wiki/WebStorage-Comments-LC-25Oct2011#LC-2

Thank you.

Noah

On 11/18/2011 10:01 AM, Arthur Barstow wrote:
> Noah - the TAG's comment has been added to the comment tracking document
> for this LC:
>
> http://www.w3.org/2008/webapps/wiki/WebStorage-Comments-LC-25Oct2011#LC-2
>
> If anyone wants to propose extensions or changes to Web Storage, please use
> [Bugzilla] and please feel free to contribute to the group's [Database]
> wiki e.g. to clarify the relationship between Web Storage and HTML5's
> AppCache.
>
> If you have any additional feedback, please reply by November 25, the day
> the CfC to publish a Candidate Recommendation of Web Storage ends [CfC].
>
> -Art Barstow
>
> [Bugzilla]
> http://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG
> [Database] http://www.w3.org/2008/webapps/wiki/Database
> [CfC] http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0998.html
>
> On 11/15/11 5:05 PM, ext Noah Mendelsohn 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 Friday, 18 November 2011 15:44:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT