RE: BER cache design (ITS#2434)

[hyc@highlandsun.com]

The entry_id is not a sufficiently unique key. You also need to reference the
backend pointer, since this cache is global to slapd and there may be
multiple backends in use.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> jongchoi@us.ibm.com
> Sent: Tuesday, April 08, 2003 8:27 PM
> To: openldap-its@OpenLDAP.org
> Subject: BER cache design (ITS#2434)
>
>
> Full_Name: Jong Hyuk Choi
> Version: HEAD
> OS: RedHat 7.3
> URL: ftp://ftp.openldap.org/incoming/ber-cache.diff
> Submission from: (NULL) (129.34.20.17)
>
>
> BER cache is a transfer content cache that stores in memory
> the attributes and
> attribute values in the form : {O[OOOO]N}{O[OOO]N}...{O[OOO]N}.
> The attribute and attribute values are taken after ACL processing.
> The cache entries are accessed using the key consisting of
> entry id and
> information on which attributes and which values are
> contained in the entry.
> The size of the entry cache is adjustable in the configuration file.
> ber-cache.diff also includes the new encoding loop patch in it.
> For more information :
> http://www.openldap.org/conf/odd-sfo-2003/jong.html
>
> - Jong
>
> ------------------------
> Jong Hyuk Choi
> IBM Thomas J. Watson Research Center - Enterprise Linux Group
> P. O. Box 218, Yorktown Heights, NY 10598
> email: jongchoi@us.ibm.com
> (phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979
>
>
>