|
I had a look at Netty today, it looks pretty good, I'll knock up a prototype....
Don't use Netty2. It has serious design flaws. I evaluated it for one of my projects. I really liked the idea. However, the implementation is broken especially performing badly in heavy load situations. Besides, the project is suspended as the author left to work on another project.
I wrote another NIO layer, based on the ideas of netty2 and hope to release it. You might want to give it a try. In fact, I wonder if I can host it here. Regards, This is long overdue, but it's not going to make it into the 1.0 release.
It's true that Netty2 is not developed further; the good news is that it is being continued in a new form under the Apache Directory project umbrella: http://directory.apache.org/subprojects/network/
 So it seems worthwile to keep an eye on this and maybe use it as network layer once it has matured. I guess (hope  this will happen much faster now since considerably more people are going to beat on it than Netty2. The project at Apache is now called MINA:
http://directory.apache.org/subprojects/mina An interesting use case for MINA is AsyncWeb (http://asyncweb.safehaus.org/
), which would make an excellent replacement for the homegrown Mule http provider. From what I read on the MINA-dev mailing list they plan a closer cooperation with AsyncWeb in the future and moving MINA to an Apache toplevel project. Some slides and demo code from the recent ApacheCon Europe '06: http://people.apache.org/~proyal/
Not going into 1.3 since it would constitute major surgery and MINA needs to mature some more as well.
Marco D'Alia has a Mule-MINA implementation: http://www.nabble.com/Asynchronous-transport-for-permanent-connections-t3357496.html
This feature is tracked in MuleForge: http://www.muleforge.org/projects/NIO
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Closed
Major
Add NIO based socket Provider
looks like a good and easy to use library which implement NIO sessions.
I am using it currently in a project.
My original plan was to write a protocol message receiver using netty.
But I am thinking know to write a generic NIO session message receiver,
and implement higher level protocol as an inbound router.