W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: Proposal for addition to WebStorage

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 28 Apr 2009 10:48:42 +0200
To: "Nikunj Mehta" <nikunj.mehta@oracle.com>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.us29fgqq64w2qv@annevk-t60.oslo.opera.com>
On Mon, 27 Apr 2009 20:23:46 +0200, Nikunj Mehta <nikunj.mehta@oracle.com>  
wrote:
> Since this question has been asked several times before in slightly  
> different ways, I have captured all the answers in one place. How does  
> BITSY differ from HTML5's ApplicationCache, Gears LocalServer, and Dojo  
> OfflineRest? See answers at  
> http://o-micron.blogspot.com/2009/04/how-is-bitsy-different-from-html-dojo.html
>
> # ApplicationCache does not allow programmatic inclusion of items  
> (dynamic entries were removed some time ago); all data capture in BITSY  
> is through an API, i.e., as a dynamic entry
> # ApplicationCache does not secure one user's private resources from  
> another; BITSY requires the presence of a specified cookie
> # ApplicationCache only responds to GET and HEAD requests; BITSY can  
> respond to arbitrary HTTP requests
> # ApplicationCache does not allow an application to intercept any  
> requests locally; BITSY allows application-defined JavaScript code to  
> intercept requests locally
> # ApplicationCache uses its own data format for identifying items for  
> local storage and exludes any other formats such as JSON and Atom; BITSY  
> does not have any format limitations
> # ApplicationCache operates per its own refresh protocol and that  
> excludes a different protocol, especially one that does not require all  
> or nothing semantics for data versioning; BITSY has no protocol  
> limitations.

So if this is a proposal to replace ApplicationCache wouldn't it be better  
to propose it to the HTML WG which is developing ApplicationCache?


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 28 April 2009 08:49:31 GMT

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