[
https://issues.apache.org/jira/browse/DIRMINA-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee resolved DIRMINA-393.
---------------------------------
Resolution: Fixed
Assignee: Trustin Lee
The following interfaces has been added:
* IoSessionAttributeMap
* IoSessionAttributeMapFactory
In the recent discussion, we decided to use existing java.util.ConcurrentMap
interface, but I realized it's not possible due to the following reasons:
* There's no way to release any resources that might have allocated from the
factory -> I added dispose() method.
* One attribute map instance might want to handle all session attribute
request. -> I added IoSession parameter to all access methods.
The default IoSessionAttributeMapFactory is almost identical with the previous
implementation.
You can set your own session attribute map factory by calling
IoService.setSessionAttributeMapFactory(...). I know it's long, but I couldn't
think of any better name.
> Allow users to choose a Map implementation for storing session attributes.
> --------------------------------------------------------------------------
>
> Key: DIRMINA-393
> URL: https://issues.apache.org/jira/browse/DIRMINA-393
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Priority: Minor
> Fix For: 2.0.0-M1
>
>
> Currently, users don't have any control over how session attributes are
> stored and managed. Adding SessionAttributesMapFactory property to IoService
> will give more control to the users, although we will have to provide the
> best generic implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
