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 akarasulu@gmail.com
 designates 209.85.212.178 as permitted sender)
MIME-Version: 1.0
Sender: akarasulu@gmail.com
In-Reply-To: <4F2FF89D.8070706@apache.org>
References: <4F2FCFEA.6090609@gmail.com>
	<8C2B4887-A662-4485-9AEF-B781555425CD@marcelot.net>
	<4F2FF89D.8070706@apache.org>
Date: Mon, 6 Feb 2012 18:15:15 +0200
Message-ID: 
 <CADwPi+H0qcXMyYiTLEZZbJTtUnzFW_EE7WuQF0dd239wwBC7JQ@mail.gmail.com>
Subject: Re: Binary attributes handling in the API
From: Alex Karasulu <akarasulu@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>,
 elecharny@apache.org
Content-Type: multipart/alternative; boundary=e89a8f13ec34bdb1d304b84df775

--e89a8f13ec34bdb1d304b84df775
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 6, 2012 at 5:58 PM, Emmanuel L=E9charny <elecharny@apache.org>w=
rote:

> On 2/6/12 4:11 PM, Pierre-Arnaud Marcelot wrote:
>
>> I believe we need this list only in the case where no schema is loaded o=
n
>> the connection, right?
>>
>
> Sadly, no. For servers that don't expose the information about the non
> human readable Syntax, we have to provide it. We use a X-IS-HUMAN-READABL=
E
> information in out LdapSyntax elements in ApacheDS, other servers don't.
>
>
>> Or, do you want to also use this list in addition to an already loaded
>> schema?
>>
>
> Yes, if needed (ie, if we can't build it from the schemas we load)
>
>
Cant we just keep this information in a constants file and make sure the
constants are accessible to the API code? Users should be allowed to
override and add more settings at runtime so more attributes can be tweaked=
?

--=20
Best Regards,
-- Alex

--e89a8f13ec34bdb1d304b84df775
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Feb 6, 2012 at 5:58 PM, Emmanuel=
 L=E9charny <span dir=3D"ltr">&lt;<a href=3D"mailto:elecharny@apache.org">e=
lecharny@apache.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<div class=3D"im">On 2/6/12 4:11 PM, Pierre-Arnaud Marcelot wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I believe we need this list only in the case where no schema is loaded on t=
he connection, right?<br>
</blockquote>
<br></div>
Sadly, no. For servers that don&#39;t expose the information about the non =
human readable Syntax, we have to provide it. We use a X-IS-HUMAN-READABLE =
information in out LdapSyntax elements in ApacheDS, other servers don&#39;t=
.<div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Or, do you want to also use this list in addition to an already loaded sche=
ma?<br>
</blockquote>
<br></div>
Yes, if needed (ie, if we can&#39;t build it from the schemas we load)<div =
class=3D"HOEnZb"><div class=3D"h5"><br></div></div></blockquote><div><br></=
div><div>Cant we just keep this information in a constants file and make su=
re the constants are accessible to the API code? Users should be allowed to=
 override and add more settings at runtime so more attributes can be tweake=
d?</div>
</div><div><br></div>-- <br><div>Best Regards,</div><div>-- Alex</div><br>

--e89a8f13ec34bdb1d304b84df775--