
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
28/Jun/05 09:08 AM
|
|
Hey, trustin, this is rick.
Arreo is about to change the underlying networking library to MINA soon. (I strongly insisted, he he. cuz they were trying to build new one -_-)
Anyway, I was thinking using MINA for all the server applications I made, yet I found out that it does not provide any good stuffs you promised to provide in MINA. No reusable codecs, no what so ever, but just plain old java.io like feature.
Heck, I read the document regarding StreamIoHandler, but no clue why should it be better than using java.io.
I don't even need a factual proof. But just wanna hear that MINA is somehow better than java.io from you. he he. ;-)
Anyway. KEEP UP THE GREAT WORK, ya doing!
I wish you the best, brother.
|
|
Description
|
Hey, trustin, this is rick.
Arreo is about to change the underlying networking library to MINA soon. (I strongly insisted, he he. cuz they were trying to build new one -_-)
Anyway, I was thinking using MINA for all the server applications I made, yet I found out that it does not provide any good stuffs you promised to provide in MINA. No reusable codecs, no what so ever, but just plain old java.io like feature.
Heck, I read the document regarding StreamIoHandler, but no clue why should it be better than using java.io.
I don't even need a factual proof. But just wanna hear that MINA is somehow better than java.io from you. he he. ;-)
Anyway. KEEP UP THE GREAT WORK, ya doing!
I wish you the best, brother. |
Show » |
|
* Reusable CODECs
It means that you can implement your own codec and reuse it for later use if it is reusable enough. For example, let's assume you've created a generic object streaming protocol codec, then you'll be able to reuse it again and again later.
* StreamIoHandler
First of all, it uses NIO and therefore it is more scalble. And it does asynchronous I/O. So there is performance gain when your business logic is blocked by other factor than network I/O (e.g. Disk I/O, database access...) There's a known performance benchmark that beats Tomcat using this technique: http://www-106.ibm.com/developerworks/library/j-nioserver/
Thanks,
Trustin