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 (athena.apache.org: domain of pajbam@gmail.com designates
 209.85.217.19 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=SifKUXz/tLBvyamjPVYo5uhpZLxfGDS3MedthD/StN8BdHqH0HessoVBZJttuheBrf
         BGCaEN6KdxSenTUxmtwhTxiGiE7pzsRRSP6zjkT6xeMi1ucPBM2oW9iwnBzMxrNiFtvQ
         UKlgIdIal1UXAaeKY2Mew5wCuogv+ju+M/Oy0=
Message-ID: <98d8c0860810020637g2ce0ee64r33f18571380f4120@mail.gmail.com>
Date: Thu, 2 Oct 2008 15:37:45 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Ldap.toString() returning a Normalized DN is an error...
In-Reply-To: <48E4CD79.9070401@nextury.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4936_19181771.1222954665983"
References: <48E4CD79.9070401@nextury.com>

------=_Part_4936_19181771.1222954665983
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Emmanuel,

On Thu, Oct 2, 2008 at 3:32 PM, Emmanuel Lecharny <elecharny@gmail.com>wrote:

> Hi guys,
>
> I'm realizing that the LdapDN.toString() method returning a normalized DN
> was a truly bad idea. It's used all over the code, for instance to generate
> error messages, and this is obfuscating them.
>
> It would be way better if the toString() method returns the user provided
> DN so that the semantic of this method is kept. All in all, the toString()
> method is supposed to return something whichj is readable by human beings,
> when 1.3.6.1.4.1.18060.0.4.0.2.1=test is not :)
>
> So what about replacing the current implementation to return the UP name
> instead of the Normname ?


I think it makes sense.
+1

Regards,
Pierre-Arnaud

------=_Part_4936_19181771.1222954665983
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi Emmanuel,<br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 3:32 PM, Emmanuel Lecharny <span dir="ltr">&lt;<a href="mailto:elecharny@gmail.com">elecharny@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys,<br>
<br>
I&#39;m realizing that the LdapDN.toString() method returning a normalized DN was a truly bad idea. It&#39;s used all over the code, for instance to generate error messages, and this is obfuscating them.<br>
<br>
It would be way better if the toString() method returns the user provided DN so that the semantic of this method is kept. All in all, the toString() method is supposed to return something whichj is readable by human beings, when 1.3.6.1.4.1.18060.0.4.0.2.1=test is not :)<br>

<br>
So what about replacing the current implementation to return the UP name instead of the Normname ?</blockquote><div><br>I think it makes sense.<br>+1<br><br>Regards,<br>Pierre-Arnaud <br></div></div><br></div>

------=_Part_4936_19181771.1222954665983--