aboutsummaryrefslogtreecommitdiffstats
path: root/libibex/testindex.c
diff options
context:
space:
mode:
authorChris Toshok <toshok@helixcode.com>2000-12-19 05:36:44 +0800
committerChris Toshok <toshok@src.gnome.org>2000-12-19 05:36:44 +0800
commit87c51e6a0a55869faf5ce3f958732c2f55807354 (patch)
treee923d54eba0d380c1c354eb19ce8f09714462911 /libibex/testindex.c
parent956ed2760e1d11c66eb1be60fdb9aa1cd9337e64 (diff)
downloadgsoc2013-evolution-87c51e6a0a55869faf5ce3f958732c2f55807354.tar.gz
gsoc2013-evolution-87c51e6a0a55869faf5ce3f958732c2f55807354.tar.zst
gsoc2013-evolution-87c51e6a0a55869faf5ce3f958732c2f55807354.zip
always use LDAP_NAME_ERROR (in the openldap1 case it's #defined to
2000-12-18 Chris Toshok <toshok@helixcode.com> * backend/pas/pas-backend-ldap.c (ldap_error_to_response): always use LDAP_NAME_ERROR (in the openldap1 case it's #defined to NAME_ERROR). (build_card_from_entry): ldap_get_values can return NULL. also, openldap2 keeps us from getting at ldap->ld_errno, so we can't tell if there was a decoding error like we used to. the double free problem where ldap would free the ber if there was a decoding problem might be fixed now.. further investigation is needed. for now we leak in openldap2. (ldap_search_handler): the ldap structure is opaque, so use ldap_search_ext to give the extra information (the max responses, timeout, etc.) in the openldap2 case. svn path=/trunk/; revision=7073
Diffstat (limited to 'libibex/testindex.c')
0 files changed, 0 insertions, 0 deletions