Hi All,

During WebApps' November 1 gathering at the TPAC, we discussed [Mins] the WG's "Programmable HTTP Caching and Serving" spec, last updated by Nikunj in January 2010 [DataCache].

During this discussion, I agreed to the following related actions:

ACTION-599 "Ask Nikunj to report the status and plans of Programmable Cache to public-webapps"
http://www.w3.org/2008/webapps/track/actions/599

ACTION-600 "Ask Oracle about their level of interest in Programmable Cache"
http://www.w3.org/2008/webapps/track/actions/600

ACTION-601 "Ask public-webapps about creating Use Cases and requirements of Program App Caches versus HTML5 App Cache"
http://www.w3.org/2008/webapps/track/actions/601

ACTION-602 "Contact julian reschke and Mark Nottingham about Data Cache"
http://www.w3.org/2008/webapps/track/actions/602

My short summary of this discussion is: it isn't clear if there is sufficient interest to continue this spec and if there is interest, what are the specific use cases it will address (i.e. use cases not addressed by HTML5 AppCache), and who is willing to commit to drive the spec forward.

-Art Barstow

[ tracker tags: ACTION-599, ACTION-600, ACTION-601, ACTION-602 ]

[Mins] http://www.w3.org/2010/11/01-webapps-minutes.html#item05
[DataCache] http://dev.w3.org/2006/webapi/DataCache/


-------- Original Message --------
Subject: ACTION-600: Ask Oracle about their level of interest in Programmable Cache (Web Applications Working Group)
Date:   Mon, 1 Nov 2010 11:40:04 +0100
From: ext Web Applications Working Group Issue Tracker <[email protected]>
Reply-To:       Web Applications Working Group WG <[email protected]>
To:     Barstow Art (Nokia-CIC/Boston) <[email protected]>



ACTION-600: Ask Oracle about their level of interest in Programmable Cache (Web 
Applications Working Group)

http://www.w3.org/2008/webapps/track/actions/600

On: Arthur Barstow
Due: 2010-11-08

If you do not want to be notified on new action items for this group, please 
update your settings at:
http://www.w3.org/2008/webapps/track/users/7672#settings

Reply via email to