Re: Revised Matched Values Draft

["Subbu K. k." <KKSUBRAMANIAM@novell.com>]

Bruce,

> Bruce Greenblatt <bgreenblatt@directory-applications.com> 07/12/00 06:28AM >>>
>...There is no obvious reason why an entry >should have 
>so many values of an attribute that an LDAP client would have a >problem 
>retrieving them all.  Do not put hundreds of values (or however >many you 
>have in mind) in the attribute......

Sorry to digress from the main point, but there are valid reasons
 why a multi-valued attribute can have a large number of values. 
Take the example of a group member list. This can run into 
thousands and possibly millions of values on the Internet. Mailing 
list servers can also build up membership lists that are large.  

While such groups can be implemented using containers there are
 both pros and cons in going that way and not everyone will be 
happy with that choice. Group vs. OU is a separate topic for 
debate.

I do see some merit in supporting a server-side filter for an attribute value read operation. This should help in bridging any 'impedance' mismatch between an LDAP client and the server.

Subbu K. K.


--------------------------------------------------------------
K. K. Subramaniam,             email: kksubramaniam@novell.com, subbu@novell.com                                   
Product Manager, NDS eDirectory (UNIX/Linux)
Novell Software, Bangalore, INDIA
Ph: +91 (80) 572-1290x2212,  (USA) 801-861-7000x42612x2206, cell:801-361-1339