Strange behaviour with netty in .net (using ikvm)

[Leandro Cruz]

Hi all.

We switched from mina to netty lately. We wrote a small client/server app
that fragments binary data to send back and forth.
When running from java the process seems to work pretty smoothly. But when
we compile it to .net using ikvm the write queue seems jammed.

In our code we call channel.write multiple times and
our ChannelFutureListener.operationComplete() is always successful, but the
message is not actually written to the other end.

I know this problem is strictly related to ikvm, not netty. But I'd like to
ask if there is anything that could be done to make sure the message is
written to the socket. Is there any write queue that I could configure? Any
know bug related to this scenario?

Cheers!

--
Leandro Rodrigo Saad Cruz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20100405/ebefea2d/attachment-0001.html