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

Re: DataCache API - editor's draft available

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 16 Jul 2009 15:54:40 -0700
Message-ID: <63df84f0907161554j1b6060b5ja22fd0bed539fb9c@mail.gmail.com>
To: "Nikunj R. Mehta" <nikunj.mehta@oracle.com>
Cc: public-webapps WG <public-webapps@w3.org>
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.

I.e. are you expecting authors to want to intercept XHR requests? Or
<img src=...> requests? Or <script src=...> requests?

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 22:55:43 UTC

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