Closed
Bug 76754
Opened 25 years ago
Closed 1 year ago
subsequent autocomplete searches should search existing results locally
Categories
(Directory Graveyard :: LDAP XPCOM SDK, defect)
Directory Graveyard
LDAP XPCOM SDK
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: dmosedale, Unassigned)
References
Details
(Keywords: perf)
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•25 years ago
|
||
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•25 years ago
|
||
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.
Updated•25 years ago
|
| Reporter | ||
Updated•25 years ago
|
Target Milestone: mozilla0.9.2 → mozilla0.9.3
| Reporter | ||
Updated•25 years ago
|
Target Milestone: mozilla0.9.3 → mozilla1.0
| Reporter | ||
Updated•24 years ago
|
QA Contact: olgac → yulian
Target Milestone: mozilla1.0 → Future
| Reporter | ||
Updated•21 years ago
|
Assignee: dmose → nobody
Status: ASSIGNED → NEW
Comment 4•18 years ago
|
||
Filter on "Nobody_NScomTLD_20080620"
Assignee: nobody → dmose
QA Contact: yulian → xpcom
Updated•14 years ago
|
Assignee: dmose → nobody
Priority: P4 → --
Target Milestone: Future → ---
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•