Hi,
in the past two weeks, I browsed the code, and I found that mina-core
could be splitted in one common project and some sub-project, namely :
- mina-future
- mina-socket
- mina-vmpipe
- mina-datagram (?)
- mina-filter-xxx (we have many filters)
The idea is to keep commons simple, and separate concerns.
The main package (common) contains 79 classes, far too much, and could
also be splitted into sub-packages.
This is just a suggestion, in order to open the discussion, I have not
established a strong position about what should be done.
There are two strong cons to this approach :
- users already using 2.0-M1 will have to fix their code
- it will now be necessary to import more than one jar
(I prefer to bring those on the table right now :)
But I think that if we don't do this kind of reorganiztion _before_ the
2.0-RC1, it will be too late and a potential 3.0 release will suffer
from the existing installed base.
I realize that those proposals may be imperfect, but the idea i really
to open the discussion.
Thoughts ?
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
