RE: Ordered list support in LDAP

[Alan Lloyd <Alan.Lloyd@OpenDirectory.com.au>]

Saurabh, we do this sort of thing in the client as the values may come
from many entries.
Its best to look at distributed searching issues (X.500 DSP) and results
merging and sorting in the server - in conjunction with what goes on in
the client.

In addition different clients may have different attribute requirements
eg. postal addresses depending on the context of the User.

regards alan

> -----Original Message-----
> From:	Saurabh Shrivastava [SMTP:SSHRIVAS@us.oracle.com]
> Sent:	Saturday, March 28, 1998 9:09 AM
> To:	ietf-ldapext@netscape.com
> Subject:	Ordered list support in LDAP
> 
> Hi,
> 
> I was wondering if there is a way to support ordered lists in LDAP
> server,
> where the order of the values is always maintained and values are
> presented
> to the clients in the same order as specified while adding these
> values.
> 
> One approach could be to use the option field in the attribute
> description {
> <AttributeDescription> ::= <AttributeType> [";" <options> ] } to
> create
> attribute subtypes which can used to tag an order to attribute values.
> A
> client can then specifically ask for <attributetype>;N where N is it's
> order
> number or have a way to understand the ordering of the values. 
> 
> e.g.: Given an attribute, say address, which can take multiple values,
> while
> creating such an entry, clients can define multiple values for
> address;1
> address;2 address;3 address;4 as 4 different values for the attribute
> address but also  implying the order 1,2,3,4 for the values.  Clients
> can
> specifically search for address;1 or address;2 or address;3 to get
> ordered
> list of values.
> 
> Is this a reasonable thing to do or are there better ways to implement
> this
> feature?
> 
> Thanks,
> 
> Saurabh Shrivastava
> Oracle Corp.				   Ph:	650-506-6815
> 500 Oracle Parkway				  Fax:	650-506-7122
> M/S 659606					email:
> sshrivas@us.oracle.com
> Redwood Shores CA-94065