[ http://issues.apache.org/jira/browse/DIRMINA-187?page=comments#action_12370079 ]
peter royal commented on DIRMINA-187: ------------------------------------- Looking closer, I prefer the solution provided in the patch. I think the question is, what is the common case? A shared IoHandler on the server, or per-session filters? In my (limited) experience, I have been using shared IoHandlers on the server w/o problems. So I'll agree with Niklas . > Support IoHandler per IoSession (SingleSessionIoHandler) > -------------------------------------------------------- > > Key: DIRMINA-187 > URL: http://issues.apache.org/jira/browse/DIRMINA-187 > Project: Directory MINA > Type: New Feature > Reporter: Simon Raess > Priority: Minor > Attachments: single-session-handler.zip > > Currently, when binding an IoAcceptor a single IoHandler is specified that is > shared among all sessions. This shared IoHandler cannot use instance > variables (without proper synchronization), because it is accessed > concurrently by multiple threads. The handler state has to be stored as > session attributes. However, if there was one IoHandler per IoSession, state > stored in instance variables of the IoHandler could be used safely. > The attached zip file contains an implemented solution (as suggested by > Niklas Therning) for this idea. See the following post in the mailing list > archive for a detailed description: > http://mail-archives.apache.org/mod_mbox/directory-mina-dev/200603.mbox/[EMAIL > PROTECTED] > What do you think? -- 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
