Hi Marv,
That makes sense. Thanks for the suggestion. It's not likely to happen
in the short term, because the API is designed to always assume that
the data has changed. However, we'll keep it in mind as we go forward.
Thanks,
~chris
On Jun 24, 2009, at 2:05 PM, SignpostMarv Martin wrote:
Well I'm thinking that the Last-Modified header might not be so
useful, but the ETag header definately would;
If the results of a query haven't changed, and then the api could
check for a matching If-None-Match request header, thus allowing an
interface lib (or in the case of the javascript api, the browser
cache) to be more responsive when dealing with queries that return
large result sets or otherwise do an extensive number of sub-queries
based on the query result (if the main query results haven't
changed, then the sub query results aren't likely to change either).
