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.184.206 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:in-reply-to:mime-version:content-type:references;
        b=CmGjnzqcCOV9MzHZwAJFuzJyP41pamw4yQaD9V97tXU0Vw/fivXIzDLsr687Y/wz9AjLujUhI7ASffaozq/RviAg8HaM7tV2oiDwitaEyKVh3Ti7jYcDZN6vLrAQB14Yba0Zjw8t5t7D/h4LfL1qtlHLRw8/RkxEmyZLMJwaQ9s=
Message-ID: <768dcb2e0511150057he5a03adi@mail.gmail.com>
Date: Tue, 15 Nov 2005 17:57:25 +0900
From: Trustin Lee <trustin@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [mina] Refactoring MINA IoFilterChain (Was: IoFilters:
 DIRMINA-121 / 122)
In-Reply-To: <43799C85.7010604@trillian.se>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9258_28859981.1132045045295"
References: <768dcb2e0511141815o35c2d25v@mail.gmail.com>
	 <43798E78.90803@trillian.se> <43799C85.7010604@trillian.se>

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

2005/11/15, Niklas Therning <niklas@trillian.se>:
>
> I just realized that when calling IoSession.write() the concrete
> IoSession implementation will always know the final destination of the
> write event. For SocketSessionImpl the final destination is always
> SocketIoProcessor.
>
> So the IoFilterChain methods for downstream events look like this:
>
> void write( IoSession session, WriteRequest writeRequest, IoProcessor p
> ) throws Exception;
>
> SocketSessionImpl's write() method looks like this:
>
> public WriteFuture write( Object message ) {
> this.filterChain.write(this, new WriteRequest(),
> SocketIoProcesso.getInstance());
> }


What is the difference from overriding the head filter of
sessionmanager-level chain to call SocketIoProcessor.flush() explicitly? We
can still get rid of SocketSessionManagerFilterChain without introducing a
new parameter.

I'll check in this change so you can see it more clearly.

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

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

<div><span class=3D"gmail_quote">2005/11/15, Niklas Therning &lt;<a href=3D=
"mailto:niklas@trillian.se">niklas@trillian.se</a>&gt;:</span><blockquote c=
lass=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); ma=
rgin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I just realized that when calling IoSession.write() the concrete<br>IoSessi=
on implementation will always know the final destination of the<br>write ev=
ent. For SocketSessionImpl the final destination is always<br>SocketIoProce=
ssor.
<br><br>So the IoFilterChain methods for downstream events look like this:<=
br><br>void write( IoSession session, WriteRequest writeRequest, IoProcesso=
r p<br>) throws Exception;<br><br>SocketSessionImpl's write() method looks =
like this:
<br><br>public WriteFuture write( Object message ) {<br>&nbsp;&nbsp;&nbsp;&=
nbsp;this.filterChain.write(this, new WriteRequest(),<br>SocketIoProcesso.g=
etInstance());<br>}</blockquote><div><br>What is the difference from overri=
ding the head filter of sessionmanager-level chain to call=20
SocketIoProcessor.flush() explicitly?&nbsp; We can still get rid of SocketS=
essionManagerFilterChain without introducing a new parameter.<br><br>I'll c=
heck in this change so you can see it more clearly.<br></div></div><br>Chee=
rs,
<br>Trustin<br>-- <br>what we call human nature is actually human habit<br>=
--<br><a href=3D"http://gleamynode.net/">http://gleamynode.net/</a>

------=_Part_9258_28859981.1132045045295--