Question

So I don’t actually mean browser caching of an Ajax request using the GET method, but storing large queries (any number, likely double-digits, of 40 – 300kb queries) in the the browser’s memory.

What are the unseen benefits, risks associated with this?

var response = JSON.parse(xhr.responseText);
Cache.push(response); // Store parsed JSON object in global variable `Cache`
// Time passes, stuff is done ...
if(Cache[query])
    load(Cache[query])
else
    Ajax(query, cache_results);

Answer 1

Is there an actual need? Or is it just optimization for the sake of? I’d suggest doing some profiling first and see where the bottlenecks lie. Remember that a web page session typically doesn’t last that long, so unless you’re using some kind of offline storage the cache won’t last that long.