[
https://issues.apache.org/jira/browse/DIRMINA-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513119
]
Yueyu Lin commented on DIRMINA-393:
-----------------------------------
Sometimes, it's needed. Especially when you developed an application server
framework that is used by other developers.
You usually told them send an request and add handler to deal with the
response. Most of them don't have much knowledge for the request size. Some of
them may send huge requests because they think your application server can
handle them. If the server cannot take this kind of burden to throw
OutOfMemoryException, your whole app server framework will be complained. I
agree in fact, in the user level, they can control the request size to simply
split big requests to small requests. But some developers may not be happy if
you ask them to do it manually.
> 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
> 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.
