Re: DataCache API - editor's draft available

On Jul 16, 2009, at 3:54 PM, Jonas Sicking wrote:

> On Thu, Jul 16, 2009 at 3:13 PM, Nikunj R. Mehta< 
> > 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- 

> 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 UTC