> So I'm still left with the question - isn't peek() supposed to be a > nonblocking way to check if a read would block? If so, why isn't it working > for me, and if not, how do I get that behavior?
No. It's a way for the processor to determine if the socket has been closed before trying to read another request (and complaining that it is incomplete). It is not supposed to be nonblocking.
