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

Niklas Therning commented on DIRMINA-42:
----------------------------------------

Yes, I can see that an IoSessionGroup could be useful as a kind of 
broadcast/multicast interface.

But, as I argued in a previous comment I don't think IoAcceptors should return 
an IoSessionMap when asking for the managed sessions. Why don't we create a new 
issue for the IoSessionGroup feature?

I'm still working on this issue. It's almost finished and the patch will also 
solve DIRMINA-93. I've added code to the VmPipe and Socket transports (inspired 
by Federico's patch) which keep track of managed sessions and closes all client 
sessions when unbind() is called. What's still missing is the method which 
returns the managed sessions. I'm thinking of adding 

Collection getManagedSessions(SocketAddress)

to IoAcceptor

and

Collection getManagedSessions() 

to IoConnector. For now I'm thinking of just copying the internal Set of 
sessions to a new Set instead of creating some smart collection impl. WDYT?

Note that I haven't done anything for Datagram transport yet. I'm not sure if 
this issue and DIRMINA-93 are applicable to datagrams?


> SessionManagers should manage list of sessions being managed.
> -------------------------------------------------------------
>
>          Key: DIRMINA-42
>          URL: http://issues.apache.org/jira/browse/DIRMINA-42
>      Project: Directory MINA
>         Type: New Feature
>     Versions: 0.7
>     Reporter: Trustin Lee
>     Assignee: Niklas Therning
>      Fix For: 0.9.1
>  Attachments: DIRMINA-42.zip
>
> Users are maintaining the list of managed sessions in acceptors and 
> connectors.  It will be much better if MINA can handle this.

-- 
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