W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

CfC: new WD of Programmable HTTP Caching and Serving; deadline January 11

From: Arthur Barstow <art.barstow@nokia.com>
Date: Mon, 4 Jan 2010 08:16:55 -0500
Message-Id: <145BB13B-D5FC-4239-9A98-8FA670C97E02@nokia.com>
To: public-webapps <public-webapps@w3.org>
This is a Call for Consensus (CfC) to publish a new Working Draft of  
Programmable HTTP Caching and Serving:


As with all of our CfCs, positive response is preferred and  
encouraged and silence will be assumed to be assent. The deadline for  
comments is 11 January.

-Regards, Art Barstow

Begin forwarded message:

> From: "ext Nikunj R. Mehta" <nikunj.mehta@oracle.com>
> Date: January 1, 2010 1:20:14 PM EST
> To: "public-webapps@w3.org WG" <public-webapps@w3.org>
> Subject: [DataCache] Editor's draft now ready for WD publication
> Archived-At: <http://www.w3.org/mid/76A64ACD-1C24-4158- 
> AF80-4A33D399123A@oracle.com>
> Happy New Year to everyone on this WG.
> I have revised the DataCache [1] draft based on feedback received so
> far. I have a couple of emails to respond to, which I will do shortly.
> At this time, this draft is ready for a new WD publication.
> The following are the major changes in this draft:
> 1. The spec extends the HTML5 ApplicationCache interface and add some
> behaviors to it related to programmability of caching.
> 2. There is no more a secure data cache concept that would be guarded
> by cookies.
> 3. This spec is heavily tied to the HTML5 Application Cache and refers
> to a lot of terms, algorithms, interfaces, and events defined there.
> It also modifies the networking model defined there.
> 5. The asynchronous interfaces are styled similar to Indexed Database.
> 6. I have removed the synchronous interface until we agree on the rest
> of the spec.
> 7. Security considerations are modified.
> 8. Mechanisms to inspect the metadata of application caches is  
> provided.
> 9. A new mechanism to annotate an application cache with outbox type
> of metadata is provided so that user agents can provide a control
> panel to users for acting on outbox when network connectivity is
> reestablished.
> 10. New events on the cache are removed or moved to events on cache
> transactions.
> 11. The File API Blob interface is now used in the spec.
> Nikunj Mehta
> http://blog.o-micron.com
> [1] http://dev.w3.org/2006/webapi/DataCache/
Received on Monday, 4 January 2010 13:17:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:22 UTC