Subject says it all really:

Can I use the KSockReadPeek flag on RSocket::RecvOneOrMore()? The docs only mention it for the two Recv() methods, but I can't use those because I have no idea how many bytes may be arriving.

I'd like to peek before "really" reading, so that I can apply flow control "back pressure" in a more fine-grained way, rather than potentially emptying the stack's buffers and reopening the TCP window with each read.

Any ideas? Has anyone tried KSockReadPeek with RecvOneOrMore()?