io::read is broken for datagrams/segments about mio HOT 5 CLOSED

I'm not sure that I am entirely following, but it seems like the solution would be to implement different versions of read() for TcpSocket vs. UdpSocket where the UdpSocket implementation is different and returns after each call to os::read(). Is that correct? I personally don't have any experience working with UDP sockets, so I can't really say.

from mio.

I actually need this functionality for TCP. It actually makes more sense for most TCP protocols, HTTP for example. Most streaming protocols are chunked up into messages that fit into segments.

When read() is called on a stream socket. It will read 1 segment and only 1 segment. I tend to ensure that messages fit inside a single segment, so if I read twice, I expect that I've received 2 messages. If something else reads for me, and it reads twice into the same buffer, now I'm left with two messages catted together that I can't parse (or am not expecting to parse)

from mio.

So I think the answer here is for read to only call read once. If you're using a stream buffer which expects to fill its buffer every time, it should just call read in its own loop, it should not be part of io, or it would be a separate function in io

from mio.

Alright, I'm OK with just removing the loop from the MIO read() API in favor of a single call to os::read()

from mio.

Resolved by 0122914

from mio.