W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: DataCache API - editor's draft available

From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
Date: Thu, 16 Jul 2009 16:17:21 -0700
Cc: public-webapps WG <public-webapps@w3.org>
Message-Id: <5FD8119C-447F-4274-962F-5D658A57B7DB@oracle.com>
To: Jonas Sicking <jonas@sicking.cc>
On Jul 16, 2009, at 3:54 PM, Jonas Sicking wrote:

> On Thu, Jul 16, 2009 at 3:13 PM, Nikunj R. Mehta<nikunj.mehta@oracle.com 
> > wrote:
>> On Jul 16, 2009, at 2:43 PM, Jonas Sicking wrote:
>>
>>> Hi Nikunj,
>>>
>>> So one of the things I've never fully understood with your  
>>> proposal is
>>> what usage patterns people are going to want to use this new API  
>>> with.
>>
>> Thanks for asking. Please ask me again if this response does not  
>> adequately
>> address your needs.
>
> Hi Nikunj,
>
> Starting over since I think you misunderstood my question.
>
> I do understand how Interceptor/DataCache works. And understand that
> it's seamless and can (based on a decision made by the browser)
> seamlessly intercept both XHR requests and <img src=..> requests.
>
> What is not entirely clear to me is how you envision that authors  
> will use it.
>

Authors will use it in all three kinds of use cases I explained  
earlier - XHR, form, and hyperlinked data. DataCache is designed to  
support all three. The intention is to accommodate any use case  
arising from the issuance of a network request when the device is off- 
line.

> I.e. are you expecting authors to want to intercept XHR requests?

For data driven applications, I expect this usage scenario.

> Or
> <img src=...> requests? Or <script src=...> requests?

<script src=...> should be adequately supported by HTML5  
(ApplicationCache), unless the src value is dynamic in nature. For the  
static case, I don't expect to see much usage of DataCache.

>
> I understand that all of this is possible, but my question is what you
> expect people to do.
>
> I hope that makes sense?
>
> / Jonas
>
Received on Thursday, 16 July 2009 23:19:42 GMT

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