18 Feb
2010
18 Feb
'10
5:21 p.m.
This method " tcp::socket::available()" really solved most of my problem
IUUC, available() cannot solve any fundamental problem, and it's bad idea to rely on it. You can use available() to perform some "speculative" blocking read, for exmaple, after your async_read_some() handler is called, but nobody can guarantee that you will not get some more data next moment, *after* you called available().