Chris Lamprecht wrote:
Very cool, thanks for posting this!
Google's feature doesn't seem to do a search on every keystroke
necessarily. Instead, it waits until you haven't typed a character
for a short period (I'm guessing about 100 or 150 milliseconds). So
Thx again for tip, I updated my
Chris Lamprecht wrote:
Very cool, thanks for posting this!
Google's feature doesn't seem to do a search on every keystroke
necessarily. Instead, it waits until you haven't typed a character
for a short period (I'm guessing about 100 or 150 milliseconds).
Ohh, good point - I was wondering how
: I also realized they're prob not doing searches at all - instead they're
: going off a DB of query popularity - I wanted to code up something
you are correct, hence the reason cnet banana doesn't appear in the list
of suggestions even though it has 41K results, but hossman trophy does
(with
Very cool, thanks for posting this!
Google's feature doesn't seem to do a search on every keystroke
necessarily. Instead, it waits until you haven't typed a character
for a short period (I'm guessing about 100 or 150 milliseconds). So
if you type fast, it doesn't hit the server until you
Google just came out with a page that gives you feedback as to how many
pages will match your query and variations on it:
http://www.google.com/webhp?complete=1hl=en
I had an unexposed experiment I had done with Lucene a few months ago
that this has inspired me to expose - it's not the same,
