[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: library questions: LDAPMessage, msgid, ...

Paul Jarc writes:
> (...)
> entry=ldap_first_entry(ld, res);
> (...)
> return entry;

BTW, have you considered simplifying the API a little?  Instead of
(ldap-{first/next}-attribute), implement (ldap-get-attributes) which
gets all the attributes in the entry.  There are unlikely to be too many
attributes in one entry for this to be a memory hog.  And maybe instead
of (ldap-{first/next}-entry), implement (ldap-get-entries) which returns
a list of entries.  This list probably already exists in memory in the
implementation, ldap_{first/next}_entry() just return pointers into the
message chain, so this too is unlikely to be a problem.  At least that's
the way the API draft is meant to be implemented.