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

Greg Duffy updated DIRMINA-162:
-------------------------------

    Attachment: mina-datagram-session-management-v2.diff

Attached is the next version with IoSessionRecycler per Trustin's and my 
comments. I still am not sure about the read buffer size issue (marked by a 
TODO in the code). Also, after some thought I don't think this is applicable to 
transports with connections (seems like too much abstraction, and doesn't fit 
well with the MINA session paradigm).

I also added a default implementation, ExpiringSessionRecycler, which uses an 
ExpiringMap to recycle sessions. It also calls sessionClosed on the session's 
filterchain when a session expires.

I hope this helps! I definitely want to contribute something nice that will 
speed MINA along to 1.0 :)

Let me know what you think!

> datagram session management fails
> ---------------------------------
>
>                 Key: DIRMINA-162
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-162
>             Project: Directory MINA
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Rainer Bieniek
>            Priority: Minor
>             Fix For: 1.0
>
>         Attachments: mina-datagram-session-management-v2.diff, 
> mina-datagram-session-management.diff
>
>
> 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

        

Reply via email to