Unexpected bytes in ByteBuffer of a TCP connection

[MichaelSteinecke]

Unexpected bytes in ByteBuffer of a TCP connection

[Aaronontheweb]

@Torgrimm yes, it's possible due to the unpredictable nature of byte buffering from the socket to have partial messages and so your decoder has to be equipped for doing that. The logic built into the LengthFrameDecoder has some handling for detecting malformed messages but it's pretty weak to be honest.

I'm not going to be making any additional fixes to the v1.4 branch of Helios - working on publishing the 2.0 spec which should make it a lot easier to handle these sorts of issues in the future.

[MichaelSteinecke]

Hello Aaron
thank you for your confirmation. When do you expect to release Helios 2.0?
Also it seems, it is not guaranteed that Streamed Connection packages (TCP) are decoded in sequence number ordering. Can you confirm this as well?