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 mrchrisallen@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:content-transfer-encoding:content-disposition:references;
        b=VpF0yZojrc7jOXGMsNGwZODod8TKGgFF0BGpx3i7Ge7xkNh8iOJBKmmB2PsEToQcno73HKxLXUvFx30CzdB3wKMKaAtRUWrOI1uIzjHcpEJ3tVQkKVwi+FlKZn1QYWnlCzdcGfLOTm4+1FiAR6oUlU8DwGrJks4pCYgvhHzqwB0=
Message-ID: <a8919d290512280547s729540d4jb3fb790d2b86f97d@mail.gmail.com>
Date: Wed, 28 Dec 2005 08:47:30 -0500
From: Chris Allen <mrchrisallen@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>,
	jvermillard@archean.fr
Subject: Re: [MINA] ReconnectFilter
In-Reply-To: <1135760094.4220.2.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <a8919d290512270812s1d2bc2afu97e2c9f00584082d@mail.gmail.com>
	 <1135700198.4195.2.camel@localhost.localdomain>
	 <a8919d290512270834pd060561of133fb4950c4e91e@mail.gmail.com>
	 <a8919d290512270856y3c09c2ecv63cfc98d6dff45a7@mail.gmail.com>
	 <a8919d290512270935j54652c84p7682434b09e61a01@mail.gmail.com>
	 <1135760094.4220.2.camel@localhost.localdomain>

Yeah, that is cool.  Sometimes you just have to get it done.  I hear ya. ;-=
)

Anyway, it's working well for me.  I did have some trouble integrating
it with Spring, as I needed reference to my IoConnection before it was
setup and passing this filter into the Application context at start up
caused a circular reference error.  I ended up handling it by making
the ReconnectionFilter implement Spring's ApplicationContectAware
interface and getting the IoConnection bean only when the closed
connection event was triggered.  I don't particularly like having this
class know about Spring, and also have\ing to know what I named the
IoConnection bean, but I couldn't think of a better solution at the
time.  If anyone has any other suggestions let me know.

I'm also planning on adding a limit to the amount of times that the
filter tries to reconnect, just in case the server it's trying to
establish the connection with really is down.

-Chris

On 12/28/05, Julien Vermillard <jvermillard@archean.fr> wrote:
>  Yes you are right, but I use it that way :
>
>  session.getFilterChain().addLast("reconnection",new
> ReconnectionFilter(2000,connector,ATMess.this,session.getRemoteAddress(),=
session.getLocalAddress()));
>
>  It was a lazy solution for postponing implemention all the constructor :=
)
>
>  Julien
>
>  Le mardi 27 d=E9cembre 2005 =E0 12:35 -0500, Chris Allen a =E9crit :
>
>
>  Hi Julien,
>
>  After writing the last email and doing a little more research, I guess t=
he
> thing to do to make your ReconnectionFilter as flexible as possible, woul=
d
> be to allow each of the IoConnector.connect() methods to work with this
> class. As you can see in the MINA JavaDocs:
> http://directory.apache.org/subprojects/network/apidocs/org/apache/mina/c=
ommon/IoConnector.html
> there are four different versions of connect() and the filter currently o=
nly
> supports one of them.
>
>  The easiest way that I can see to accomplish this is to provide multiple
> constructors for the ReconnectionFilter class that account for each of th=
ese
> connection methods.  I've currently added my own with the single
> SocketAddress, but for a truly flexible filter I guess it would have to
> support the others as well.
>
>  Anyway, I know this is a work in progress, but I just thought that I sho=
uld
> mention it, even though it's super obvious.
>
>  Thanks again for letting me know where to find this class, and for creat=
ing
> it in the first place.
>
>  -Chris