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

[whatwg] JSONRequest

From: Douglas Crockford <douglas@crockford.com>
Date: Sat, 18 Mar 2006 16:13:52 -0800
Message-ID: <441CA240.1030207@crockford.com>
 > 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.

Caching is a deal with the devil, in which reliability is traded off for 
performance. For some applications, such as the delivery of static documents and 
images, it can be a pretty good bargain. As you move to the dynamic end of the 
spectrum, it becomes a very bad bargain.

I see JSONRequest as a device for delivering the most dynamic of data. In such 
applications, I see caching diminishing reliability, and with reliability goes 
security.

My intention with JSONRequest is to make it minimal because being minimal will 
make it easier to understand and easier to implement correctly.

It is not my intention to replace anything. All of the existing document 
delivery mechanisms continue to have a mission. JSONRequest's mission is to 
deliver dynamic data. Currently, there is no good mechanism for do that.

Your assumption about Yahoo is at best misinformed.
Received on Saturday, 18 March 2006 16:13:52 UTC

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