W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2006

[whatwg] JSONRequest

From: Jim Ley <jim.ley@gmail.com>
Date: Sat, 18 Mar 2006 00:51:25 +0000
Message-ID: <851c8d310603171651h53949affi535a1955cffdffca@mail.gmail.com>
On 3/17/06, Douglas Crockford <douglas at crockford.com> wrote:
> > The cache rules are unworkable, please remove these and use standard
> > HTTP methods for suggesting the cacheability of a resource, forcing
> > them to be uncacheable is unworkable w.r.t. to proxy caches and
> > extremely unwelcome within the browser.
>
>   Applications must not cache responses to a POST request because the
>   application has no way of knowing that the server would return an
>   equivalent response on some future request.

Of course the application can know that, that's what HTTP cache
control headers are for, the cacheability of a resource is easy to
advertise, and all browsers should know it.

Please explain your use cases for making no JSONRequest cacheable, it
really is completely silly to me and an absolute deal breaker, I
assume it's because working for yahoo you need not worry about such
things as bandwidth and cost.

Jim.
Received on Friday, 17 March 2006 16:51:25 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:45 UTC