Hi Trustin !
This is great news.
+1 of course, but I will just raise one concern :
DIRMINA-159 is tagged as closed, but it should point to DIRMINA-163
which has been reopened. This is a potential serious issue, and users
must at least be warned about it.
It would be very cool if we can have a clear status about this problem,
is it really an IPV6 issue or something else. If I'm wrong and that it's
not IPV6 related, then we have to investigate where the problem come
from. Ersin, Alex and I experienced it on different computers and
different Linux System (FC4 and Ubuntu), and, aside the java property I
set, we don't have any fix for those two Jiraes.
I also think that setting a java property is *not* the proper solution.
Congratulation for this version ! Great work Trustin, Niklas and all the
contributors !
Trustin Lee a écrit :
Hi all,
As you see from here
<http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10670&fixfor=12310371>,
we fixed quite a lot of issues since we released MINA 0.9.0. I think
it's now to release MINA 0.9.1 so users benefit from the new release.
Most notable changes are:
* Migration to Maven 2
* You can get a collection of managed sessions by calling
IoAcceptor.getManagedSessions( SocketAddress )
* MINA closes all client sessions when you unbind the service
automatically. (You can disable it, too.)
* Netty2 integration classes in org.apache.mina.filter.codec.netty
(Thanks, Julien!)
Please note that this release will not include the changes I've made
in my sandbox. Niklas and I concluded that we need more discussion on
the new API though it makes MINA easier for new users to use. Please
reply to the message I've sent a few days ago about this issue, so we
can include the changes in 0.9.2.
[x] +1, Release
[ ] 0, Abstain
[ ] -1, Don't release
Cheers,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/ <http://gleamynode.net/>
PGP Key ID: 0x854B996C
