Hi list,

I'm using the excellent autocomplete plugin from bassistance.de. The cache
and subset matching features are very useful.

I would like to take the subset matching a bit further. I want to prevent
the script from querying the server if the query string does not match
anything from a previous result set in which the current query is a
potential subset of. I apologize for being unclear, I know I'm misusing the
terms here. I hope I could explain it better with an example.

A user types 'foo', which calls a server script that returns ['foo',
'foobar', 'foobarbaz']. The user then types 'b'. Because of subset matching,
a query for 'foob' is not sent anymore, and the current set is still used.
If the user then types 'u', which matches nothing in the result set, the
script takes a trip to the server. That trip is useless since all words with
'foo' have already been obtained. A query for 'foobu' will not return
anything. My goal is to prevent that trip to ease the server load a little.

Another thing, I bound a blur handler for the autocompleted element which
calls search() so that I could display a message if there are no matches
found, as per a recommendation I found in this list's archive. My problem is
that the search() method triggers another server query, which is useless
since I already know that there are no matches. Is there a better way to
display a 'no match' message which doesn't need to ask the server?

Any guidance regarding these matters would be highly appreciated.

Thanks,
-- 
   -- Mon

Reply via email to