To clarify what I was saying.
If we were to augment the remoting API to add methods that take ByteBuffers[] (or byte[]
or whatever) for both receiving and sending, then in the non blocking case we would have
to cope with partial sends and receives in the application.
We could of course build intelligence into the API to cope with the partial sends
/receives - but this is pretty much the raison d'etre for NIO frameworks such as MINA
AFAIK. So we'd be re-inventing the wheel.
If we didn't build that intelligence into the API, then we would have to handle it
ourselves in the application layer, which again would be re-inventing the wheel, this time
in the application.
If we agree that we don't want to build our own NIO framework then, I suggest we
should just use one that we know works already.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980363#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...