How google suggest caches queries on client side?

Well, I was playing with Google query auto completion and noticed funny thing: if I for example type in “m” letter, it performs Ajax jsonp query. Then if I’ll refresh my page and enter “m” letter again there would not be any query. The same thing happens with longer sequences of letters.

It’s obvious that Google uses some client-side caching. And I’m quite positive that it doesn’t store anything in cookies. I know some technologies that allow to cache large amounts of data on client side for JS use, but I’d like to know which one Google uses?

  • Autosuggestion Javascript/PHP/AJAX Code
  • “suggest” feature for textboxes in a rails app
  • Auto suggest with two input boxes
  • Efficient AutoSuggest with jQuery?
  • Auto complete doesn't work
  • How to implement a google suggest-like input field?
  • Their code is awfully obfuscated and it’ll take me some time to find the answer by myself, so if someone will point me any descent up to date article about Google suggest that answers my question, I’d be very grateful.

  • Efficient AutoSuggest with jQuery?
  • Google's predictive text as you type code example - w/o auto suggest dropdown menu
  • Searching for multiple partial phrases so that one original phrase can not match multiple search phrases
  • Auto suggest with two input boxes
  • Auto complete doesn't work
  • Autosuggestion Javascript/PHP/AJAX Code
  • One Solution collect form web for “How google suggest caches queries on client side?”

    It’s the browser that handles the caching. Google just implement all the relevant headers (eg Expires) to make sure the script is cached correctly, then the next time it’s requested the browser fetches it from the cache. No fancy tricks or google magic going on 🙂

    EDIT: Best link I could find was http://code.google.com/speed/page-speed/docs/caching.html. Maybe someone else can point out some other links.