Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1820075678.1137668742877.JavaMail.jira@ajax.apache.org>
Date: Thu, 19 Jan 2006 12:05:42 +0100 (CET)
From: "Rainer Bieniek (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRMINA-162) datagram session management fails
In-Reply-To: <841723789.1136933781031.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIRMINA-162?page=comments#action_12363234 ] 

Rainer Bieniek commented on DIRMINA-162:
----------------------------------------

I already approached this but I found out that it will not work without a acceptor facade which encapsulates the "real" datagram acceptor and does the session tarcking on behalf of
the client. This thing is in fact second-next on my to-do list for my current project. 
Once this facade works, it can easily implement the proposed tracker interface. If it works, I will supply my implementation as a diff to mina-0.9.0

> datagram session management fails
> ---------------------------------
>
>          Key: DIRMINA-162
>          URL: http://issues.apache.org/jira/browse/DIRMINA-162
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.9
>     Reporter: Rainer Bieniek
>     Priority: Minor

>
> As of mina 0.9.0 the session management does not work in various ways:
> - a new session is created per received package. The worker thread does not cache created session but only assign the select key to the session and drops it after processing the package. It would be better to attach the session to the RegistrationRequest and check it while processing the received package.
> - the provided IoFilterChainBuilder does get applied to the created datagram session. It is cached in the RegistrationRequest but not used on the session
> - The sessionClose lifecycle event is not applied on the session either. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira