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

Re: Returning single values from multivalued attributes

To: mcs@netscape.com (Mark C Smith), d.w.chadwick@salford.ac.uk
Subject: Re: Returning single values from multivalued attributes
From: Bruce Greenblatt <bgreenblatt@dtasi.com>
Date: Tue, 10 Aug 1999 08:19:43 -0700
Cc: ietf-ldapext@netscape.com
In-reply-to: <37AF1B21.775F960C@netscape.com>
References: <E11CtbI-0000KT-00@tantalum.btinternet.com>
Resent-date: Tue, 10 Aug 1999 08:19:59 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"ua7lHB.A.3YF.YMEs3"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

I'm a little confused by this.  My perspective is that the requirements for
this new functionality arise almost entirely from poor Schema/DIT design.
I certainly agree that if you put 1000s of certificates in a single
attribute, you will have difficulty retrieving a single certificate
instance from the entry inquestion.  The obvious solution to this problem
is NOT to enhance LDAP (or DAP for that matter).  The obvious solution IS
"don't put 1000s of certificates in a single attribute".

Bruce
==============================================
Bruce Greenblatt
Directory Tools and Application Services, Inc.
http://www.directory-applications.com

References:
- Re: Returning single values from multivalued attributes
  - From: David Chadwick <d.w.chadwick@salford.ac.uk>
- Re: Returning single values from multivalued attributes
  - From: mcs@netscape.com (Mark C Smith)

Prev by Date: Re: Returning single values from multivalued attributes
Next by Date: RE: Returning single values from multivalued attributes
Index(es):
- Chronological
- Thread