Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com
 designates 209.85.212.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=DRoVGhnxPMUlBs3VwY1v/jChYdcAYb0kJFuMuzEFU8m/ffcG5P3SKp1E0VaS9Bx8hA
         Y3En6dfU+EFJGbAYJd2Nj6Rk2odPb/X14T5yYIknVXof3zwPHL/50dp4gR3f/HjamRfA
         J85waPYwU95nJy04xj/eX3CFY7tE5k/Q76YAE=
MIME-Version: 1.0
Sender: ayyagarikiran@gmail.com
In-Reply-To: <AANLkTi=tAsmS61OYxMOYmfVLWR8L_o6hPsWKSPQfDWa0@mail.gmail.com>
References: <4D5A9A61.8060507@gmail.com>
	<AANLkTimHL=xbz6bgYgBRxE9GbRWR_r2qkZck4njbmH89@mail.gmail.com>
	<4D5ACF66.6080800@gmail.com>
	<AANLkTik0JZYy36NbS5_tHq3XU+CdOPWnp8LA5hhOr19L@mail.gmail.com>
	<4D5AE009.20107@gmail.com>
	<AANLkTi=tAsmS61OYxMOYmfVLWR8L_o6hPsWKSPQfDWa0@mail.gmail.com>
Date: Wed, 16 Feb 2011 02:22:55 +0530
Message-ID: <AANLkTims+ctpPbcY8Fm5eRBXKySCmOZXYqPULrXp-6yr@mail.gmail.com>
Subject: Re: Dn should probably not implement Comparable
From: Kiran Ayyagari <kayyagari@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 16, 2011 at 2:15 AM, Kiran Ayyagari <kayyagari@apache.org> wrot=
e:
> On Wed, Feb 16, 2011 at 1:50 AM, Emmanuel Lecharny <elecharny@gmail.com> =
wrote:
>> On 2/15/11 9:15 PM, Kiran Ayyagari wrote:
>>>
>>> On Wed, Feb 16, 2011 at 12:39 AM, Emmanuel Lecharny<elecharny@gmail.com=
>
>>> =A0wrote:
>>>>
>>>> On 2/15/11 8:00 PM, Kiran Ayyagari wrote:
>>>>>
>>>>> On Tue, Feb 15, 2011 at 8:53 PM, Emmanuel Lecharny<elecharny@gmail.co=
m>
>>>>> =A0wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> the compareTo method has a semantic that probably does not applies t=
o
>>>>>> the
>>>>>> Dn
>>>>>> class : either two DNs are equals, or they are different, but they
>>>>>> aren't
>>>>>> superior or inferior, except if one is the parent of the other.
>>>>>>
>>>>>> As we already have a isParent and isChild methods, I suggest we remo=
ve
>>>>>> the
>>>>>> compareTo() methods (which is never used) and not implemen the
>>>>>> Comparable<Dn> =A0 =A0interface.
>>>>>>
>>>>> I suggest we keep this, think of ordering the Entry objects while
>>>>> performing an export
>>>>> (sorting a huge number of entries won't be the ideal case, but when w=
e
>>>>> have a few entries which are fetched in an adhoc manner(i.e without
>>>>> performing repetitive one level searches))
>>>>
>>>> The thing is that there is no way to order a list of DNs, as there is =
no
>>>> such a MatchingRule as DnOrderingMatch. How do you order two DNs which
>>>> RDN
>>>> don't have the same AttributeType ?
>>>>
>>>> I have checked RFC 4517, and after having read it, I saw that comparin=
g
>>>> two
>>>> DNs is just meant to check that they are equal, or not. No order is
>>>> implied.
>>>
>>> how about using the isParent() and isChild() methods for that inside
>>> the compareTo()
>>
>> yes, but still it's not possible to compare 2 DNs with the same parent..=
.
>> CompareTo() for DNs simply does not make sense :)
> hmmm, just wondering why can't we compare the normalized values(which
> are strings) of two DNs
by the above I mean for equality, and we have isParent() if it is
higher in hierarchy and isChild() otherwise,
I see that semantically it doesn't make *much* sense to say 'compare
two DNs' but still we can *order* DNs and
that is where this method is helpful
>>
>>
>> --
>> Regards,
>> Cordialement,
>> Emmanuel L=E9charny
>> www.iktek.com
>>
>>
>
>
>
> --
> Kiran Ayyagari
>


--=20
Kiran Ayyagari