directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Federico Bonelli (JIRA)" <>
Subject [jira] Commented: (DIRMINA-42) SessionManagers should manage list of sessions being managed.
Date Tue, 13 Dec 2005 22:34:49 GMT
    [ ] 

Federico Bonelli commented on DIRMINA-42:

Yes, I planned to work it out because I need to resolve DIRMINA-93 for my applications.

Well, I'd like to work at this, but I'm new to team-development tecnique (I always worked
alone), so I need a large amount of tips, i'd like to discuss every single choice.

I was thinking about that, about the hashMap vs Collection, and I don't know. I have many
structure that need of a unique identifier that match every single connection, in my applications,
but for every application my key is different.

I'm thinking about an ftp server that need of couple nick-ipaddr, about a chat server that
need only ipaddr before login, then the nick after login, the neededs of every application
is protocol specified...

For mina purpouse only (DIRMINA-93) a collection is all we need, but if we want to make this
IoSessionMap usable for the highlevel application we need to develop a userdefinable hashing,
pointing to our own collection, or maybe to another parallel mina-useless data structure dedicated
for user-usage (that's the goal of DIRMINA-42)

So the key problem is worse then I thougth. What do you think about it?

> SessionManagers should manage list of sessions being managed.
> -------------------------------------------------------------
>          Key: DIRMINA-42
>          URL:
>      Project: Directory MINA
>         Type: New Feature
>     Versions: 0.7
>     Reporter: Trustin Lee
>     Assignee: Niklas Therning
>      Fix For: 0.9.1

> 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:
For more information on JIRA, see:

View raw message