RXTX: data might not *yet* be available

[jeje]

This is a fix for issue #958

[normanmaurer]

doRead(..) should never been called before it is connected.. Can you give some more details ?

[jeje]

I don't think it's called before it's connected. But the issue is that return buf.writeBytes(in, buf.writableBytes()); blocks and never returns, even when some data is available later on...

BTW, I don't understand the above code. Shouldn't it be return buf.writeBytes(in, in.available()); instead?
Otherwise we're asking to copy a length of data (buf.writableBytes()) which might be bigger than in.available() and potentially wait for a really long time 'til there is enough data sent from the serial port.

Can you confirm that doRead() is not called unless available() returns a non-zero value?

[normanmaurer]

@jeje I just fixed the read code which was not correct. So thanks for point it out :) Could you retry with latest master ?

[jeje]

This works just fine! Thanks for this commit.

I saw that you took the opportunity to refactor the OioSocketChannel class which had the exact same issue ;-)

This pull-request and issue #958 can be closed.

[normanmaurer]

Fixed by #962