douglas at crockford.com
Sat Mar 18 16:13:52 PST 2006
> 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
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.
More information about the whatwg