channel.read has side effect without type representation about zio-nio HOT 3 OPEN

@ubourdon I don't think there is any concept of "read all" from a Socket's point of view.
Socket's keep sending and receiving messages until they are closed. Buffer's, on the other hand, have a finite capacity and so have a concept of "final" and "end of file".

Typically if you are implementing an HTTP server, you "reading" any message that comes in, until a \r\n is received, which will mark the end of an HTTP request.

from zio-nio.

To do that, you must specify a buffer size and read this size several time until you find \r\n no ?

from zio-nio.

But beyond that,

channel.read mutate the state of channel without any type returned by the action.

channel.read don't return same result if i call it 2 or moe times, that brake the Referential transparency principle.

from zio-nio.