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 (asf.osuosl.org: domain of trustin@gmail.com designates
 64.233.162.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=PRjvpA0MAQaZnBmwvw010YLuaKfHB7kaUSJsHpWype8eh9oAso/LZuaDMhgZmDzl7auBxWRoVMVM7bnIv/Gh1wOOob0P6ltLJb96eGLgBMpUg4uD6/A0brGLHeeFbLChzGipt/RUUyjtnFbGAh3ckN/UNyFgTd9GR9pbeuiOolc=
Message-ID: <768dcb2e05092219565a116bfd@mail.gmail.com>
Date: Fri, 23 Sep 2005 11:56:01 +0900
From: Trustin Lee <trustin@gmail.com>
Reply-To: Trustin Lee <trustin@gmail.com>
To: Norbet Reilly <nrhope@gmail.com>,
	Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: DIREVE-253
In-Reply-To: <f275eef1050922165547ed513e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7893_1856739.1127444161286"
References: <f275eef1050922165547ed513e@mail.gmail.com>

------=_Part_7893_1856739.1127444161286
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Norbert,

2005/9/23, Norbet Reilly <nrhope@gmail.com>:
>
> Hi Trustin,
>  Just thought I might mention this issue to you as well, as I gather from
> your postings that you are the MINA guru, and my limitted understanding o=
f
> the root cause under this issue leads me to suspect that the MINA level m=
ay
> be involved in some way.
>

MINA is just a network application framework. It doesn't have relationship
with escaping IMHO. You'd better to look at the LDAP protocol handler and
LDAP codec. You can locate them at:

* protocol-providers\ldap\trunk
* shared\ldap\trunk

I know you guys are really busy, but if you get a second to scan the issue
> (and reassign the component if reqd) that would be great. I'm happy to
> investigate further but don't really know how to go about it, so if there
> are any simple pointers about how to investigate further I'll hop to it. =
For
> instance I'm not sure why URL encoding gets into the LDAP results picture=
 at
> all, and where it might be occuring in the code.
>

I didn't look into the codec part, so I cannot tell you why URL encoding
gets into LDAP. Perhaps Alex or Emmanuel could help us here.

Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/

------=_Part_7893_1856739.1127444161286
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Norbert,<br><br><div><span class=3D"gmail_quote">2005/9/23, Norbet Reill=
y &lt;<a href=3D"mailto:nrhope@gmail.com">nrhope@gmail.com</a>&gt;:</span><=
blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 2=
04, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Hi Trustin,</div>
<div>&nbsp;</div>
<div>Just thought I might mention this issue to you as well, as I gather fr=
om your postings that you are the MINA guru, and my limitted understanding =
of the root cause under this issue leads me to suspect that the MINA level =
may be involved in some way.
</div></blockquote><div><br>MINA is just a network application framework.&n=
bsp; It doesn't have relationship with escaping IMHO.&nbsp; You'd better to=
 look at the LDAP protocol handler and LDAP codec. You can locate them at:<=
br><br>
* protocol-providers\ldap\trunk<br>* shared\ldap\trunk<br></div><br><blockq=
uote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 20=
4); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>I know you guys are=
 really busy, but if you get a second to scan the issue (and reassign the c=
omponent if reqd) that would be great. I'm happy to investigate further but=
 don't really know how to go about it, so if there are any simple pointers =
about how to investigate further I'll hop to it. For instance I'm not sure =
why URL encoding gets into the LDAP results picture at all, and where it mi=
ght be occuring in the code.
</div></blockquote><div><br>I didn't look into the codec part, so I cannot =
tell you why URL encoding gets into LDAP.&nbsp; Perhaps Alex or Emmanuel co=
uld help us here.<br><br>Trustin<br></div></div>-- <br>what we call human n=
ature is actually human habit
<br>--<br><a href=3D"http://gleamynode.net/">http://gleamynode.net/</a>

------=_Part_7893_1856739.1127444161286--