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.182.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=L36+lJoh9zbKjRhZyfKPEIqhbdOdlTHXTASHiS7h/2jjUYSVkbYqXxK8zoQ8fh25037LH8blW5R2j/ERXTgyRroO6gRRgPdnigxEIGYb0gy7kheQatnN1A68Zc8iu+ZKGt7YD1hHr3eR5s8aNUP7+WRS5o/SqgiG3+Xaj9vG4wg=
Message-ID: <768dcb2e0602250110i304d6990kd4eec16f138d97cf@mail.gmail.com>
Date: Sat, 25 Feb 2006 18:10:54 +0900
From: "Trustin Lee" <trustin@gmail.com>
To: mina-dev@directory.apache.org
Subject: Re: [mina] DIRMINA-165 revisited
Cc: "joshua portway" <joshlists@stain.org>,
	"Apache Directory Developers List" <dev@directory.apache.org>
In-Reply-To: <5FB63612-B3F9-41DD-9AD9-EB0D9DF6482A@stain.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_24722_14117374.1140858654137"
References: <510E6791-0FD2-49CB-9736-39261BBB367C@stain.org>
	 <000e01c6326b$38d91c80$0300a8c0@fedechiccowinxp>
	 <5FB63612-B3F9-41DD-9AD9-EB0D9DF6482A@stain.org>

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

On 2/16/06, joshua portway <joshlists@stain.org> wrote:
>
> thanks for the warning - is anyone actively working on this issue ?


Not yet unfortunately.  Any contribution is welcome.  ;)

It's important to my project to be able to slice buffers ( actually,
> I have one permanent buffer, with permanent "slice" buffers pointing
> to bits of it and when the contents of the buffer change I send a
> load of network messages - one for each of the slice buffers - this
> avoids any copying or reallocating buffers ).


We understand your point clearly.  We'll resolve this issue with careful
discussion.

If no one else is working on this I'll probably give it a go myself,
> but I would appreciate some advice about why it was considered a bad
> idea for view buffer "containers" (mina ByteBuffer) to be pooled -
> can anyone help me out here ?


It is because it is very hard to keep track of NIO buffers.  It becomes ver=
y
error-prone for a user to release the buffer while its duplicate or slice i=
s
being used by others.  There should be a trade-off somewhere to achieve
duplication and slicing of buffers.  Let's keep discussing on this issue in
the JIRA:

http://issues.apache.org/jira/browse/DIRMINA-165

Thanks,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

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

On 2/16/06, <b class=3D"gmail_sendername">joshua portway</b> &lt;<a href=3D=
"mailto:joshlists@stain.org">joshlists@stain.org</a>&gt; wrote:<div><span c=
lass=3D"gmail_quote"></span><blockquote class=3D"gmail_quote" style=3D"bord=
er-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-l=
eft: 1ex;">
thanks for the warning - is anyone actively working on this issue ?</blockq=
uote><div><br>Not yet unfortunately.&nbsp; Any contribution is welcome.&nbs=
p; ;)<br></div><br><blockquote class=3D"gmail_quote" style=3D"border-left: =
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;=
">
It's important to my project to be able to slice buffers ( actually,<br>I h=
ave one permanent buffer, with permanent &quot;slice&quot; buffers pointing=
<br>to bits of it and when the contents of the buffer change I send a<br>
load of network messages - one for each of the slice buffers - this<br>avoi=
ds any copying or reallocating buffers ).</blockquote><div><br>We understan=
d your point clearly.&nbsp; We'll resolve this issue with careful discussio=
n.
<br></div><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px s=
olid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If =
no one else is working on this I'll probably give it a go myself,<br>but I =
would appreciate some advice about why it was considered a bad
<br>idea for view buffer &quot;containers&quot; (mina ByteBuffer) to be poo=
led -<br>can anyone help me out here ?</blockquote><div><br>It is because i=
t is very hard to keep track of NIO buffers.&nbsp; It becomes very error-pr=
one for a user to release the buffer while its duplicate or slice is being =
used by others.&nbsp; There should be a trade-off somewhere to achieve dupl=
ication and slicing of buffers.&nbsp; Let's keep discussing on this issue i=
n the JIRA:
<br><br><a href=3D"http://issues.apache.org/jira/browse/DIRMINA-165">http:/=
/issues.apache.org/jira/browse/DIRMINA-165</a><br><br>Thanks,<br>Trustin<br=
></div></div>-- <br>what we call human nature is actually human habit<br>
--<br><a href=3D"http://gleamynode.net/">http://gleamynode.net/</a><br>--<b=
r>PGP key fingerprints:<br>* E167 E6AF E73A CBCE EE41&nbsp;&nbsp;4A29 544D =
DE48 FE95 4E7E<br>* B693 628E 6047 4F8F CFA4&nbsp;&nbsp;455E 1C62 A7DC 0255=
 ECA6

------=_Part_24722_14117374.1140858654137--