76754 - subsequent autocomplete searches should search existing results locally

Status: NEW

(Directory :: LDAP XPCOM SDK, defect)

Description

[Dan Mosedale (:dmosedale, :dmose)]

Right now, all LDAP autocomplete searches hit the server.  For performance
reasons, and so that we don't unnecessarily hammer LDAP servers, this should be
changed so that searches which drill-down on a previous result just look at the
local result set.

Comment 1

[Leif Hedstrom]

Also remember that if you do this, you might have to analyze the search filter
string (user preference) to see when you need to redo the LDAP search. Or at a
minimum, figure out under exactly what conditions a new LDAP search must be
issued. For instance, if the search filter is

   (cn=%1* %2*)

If the User types "lei" you can only reuse the data from the first search up
until the first space is type, then you need to get a new dataset from LDAP. 

This could quickly get complicated, depending on how much flexibility we allow
in the user configurable search filters.

Comment 2

[Leif Hedstrom]

Hmmm, that was probably a bad example, but I'm sure there are search filter
strings that can be constructed that will cause a different search to be issued
against the LDAP server... :) Remember that searches can be "nested" with "and"
and "or" operations as well.

Rheet.

Comment 3

[yulian chang]

reassign to Olga as QA contact

Comment 4

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"