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

Re: entryDN attribute (or entryUUID?)

To: Pierangelo Masarati <ando@sys-net.it>
Subject: Re: entryDN attribute (or entryUUID?)
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Thu, 22 Feb 2007 21:50:14 +0100
Cc: "P. Martinez" <martinezino@googlemail.com>, openldap-software@openldap.org
In-reply-to: <45DDF73C.2070500@sys-net.it>
References: <45DB8392.8010006@ma.rr.com> <hbf.20070221xhw0@bombur.uio.no> <1c226c31ec7f03796fd01153c77f0f45@googlemail.com> <45DDF73C.2070500@sys-net.it>

Pierangelo Masarati writes:
>> I plan to write an search interface and was thinking about tracking
>> results ...
>
> entryUUID is a perfect key, since it has the above properties and it's
> fixed length.

Also he doesn't need to parse it if he wants to know if the directory
would consider two values equivalent.
Unlike how DN "CN=Foo+UID=bar" matches "uid=bar+cn=foo".

> However, in general it's not something an interface would
> expose.

-- 
Regards,
Hallvard

Follow-Ups:
- Re: entryDN attribute (or entryUUID?)
  - From: "P. Martinez" <martinezino@googlemail.com>

References:
- entryDN attribute
  - From: Brandon McCombs <bmccombs@ma.rr.com>
- Re: entryDN attribute
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: entryDN attribute (or entryUUID?)
  - From: "P. Martinez" <martinezino@googlemail.com>
- Re: entryDN attribute (or entryUUID?)
  - From: Pierangelo Masarati <ando@sys-net.it>

Prev by Date: Re: entryDN attribute (or entryUUID?)
Next by Date: Re: entryDN attribute (or entryUUID?)
Index(es):
- Chronological
- Thread