Chris, Thanks for the prompt response.
I do have an openldap server. I installed it on my RedHat 7.2 system using the RPM package shipped by RedHat. I checked my configuration, it had subinitial indices for cn and mail. I turned on sub indices for cn and displayName. However, I still see quite long latencies. After I type in the substring/prefix, it takes anywhere between 6-15 seconds for the window with expanded names to pop up. While I am waiting, there is no indication whether the LDAP server already returned a null result for the query, or whether the query is still in progress. Yatin On Tue, 2002-03-12 at 13:13, Chris Toshok wrote: > Do you have indexing turned on for the cn and mail fields? evolution > presently does a prefix search on mail and a substring search on cn, so > "mail=foo*" and "cn=*foo*". oh, and it also does a prefix search on > displayName, so indexing that might help too. > > Is this an openldap server? by default the only indexing turned on for > them is on objectClass. > > Chris > > > > > I tried the latest evolution snapshot. The response time for evo to resolve > > a name from the LDAP server as I type into the To: or Cc: boxes still seems > > too long. My LDAP server is one hop away on a local LAN from my evo client > > machine. I think part of the problem may be that there is no visual > > indication that the application is still waiting for a response from the > > LDAP server. So the user has no idea as to what is actually going on. > > > > The auto-completion for LDAP is great when it works smoothly and quickly. > > But, its current latency is an issue for me. I wish I could simply type in > > a comma-separated list of portions of names or email addresses, and then > > press a single key to expand all of those names/addresses from the LDAP > > server. Most often I have exactly one contact for each expansion and those > > should be expanded without any further user intervention. Currently, for > > each address, I need to wait an indeterminate amount of time without > > feedback as to whether the query to the LDAP server succeeded or not, then > > use the Down arrow followed by the Return key to expand each of these > > common-case addresses. The single-key-press expansion would eliminate that, > > and the UI could pop up a box or change the mouse cursor to a > > watch/hourglass to indicate that it is checking the addresses against the > > LDAP server. In the few cases that there are multiple possible expansions, > > evo could display all of the possibilities to allow the user to pick one as > > it already does. I use this feature very often with Outlook Express (press > > Ctl-K to resolve addresses from the LDAP server) and would love to have it > > in Evo as well. > > > > I know that incorporating this instead of auto-completion would result in > > conflicting user interfaces depending on whether you use a local Contacts > > folder or an LDAP-based addressbook, but in my opinion, the latency of LDAP > > servers justifies having this different UI. > > > > Any thoughts? > > > > Yatin _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
