Re: objectClass in entry attribute order

[Michael Ströder <michael@stroeder.com>]

Dave Horsfall wrote:
> On Wed, 14 Feb 2007, Donn Cave wrote:
> 
> [...]
> 
>> I don't that I have ever seen objectClass appear anywhere but at the top 
>> of the entry, before this.  Evidently it isn't a serious problem - these 
>> entries are still retrievable, modifiable and slapadd works on them.
> 
> Order doesn't matter, but current behaviour seems to be first in first
> out or something, thus when you modify an attribute it propagates to the end
> of the list.

Additionally any client or server implementation relying on some kind of
attribute order or attribute value order is broken. And the order in the
LDIF does not necessarily say anything about the order in the internal
representation or the order in the LDAPResult message.

> Yeah, it looks funny, but end users aren't supposed to "see" raw LDIF.

Yupp. No problem at all if the clients are not broken.

Ciao, Michael.