Re: the 4th parameter of 'recv' function, 0?

That's the normal case and I imagine 99% of the socket code
out there uses no special flags.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A61396CC-19F5-4BCF-AF1F-3945961BC061@xxxxxxxxxxxxxxxx
in the Bluetooth sample 'bthcxn' of the Windows SDK v6.1 :
iLengthReceived = recv(ClientSocket,
pszDataBufferIndex,
(CXN_TRANSFER_DATA_LENGTH -
uiTotalLengthReceived),
0);
From the MSDN http://msdn.microsoft.com/en-us/library/ms740121(VS.85).aspx
I know there are three values of the 'flag' in function recv.
MSG_PEEK 0x1
MSG_OOB 0x2
MSG_WAITALL 0x4
what is '0' represent for? How it influence the behavior of the function
'recv'?
Is there something else I can refer to?

Best Regards!




.

Loading