Re: the 4th parameter of 'recv' function, 0?
- From: freefox <robert.locke@xxxxxxxxxxxxxxxx>
- Date: Tue, 12 Aug 2008 02:03:20 -0700 (PDT)
On 11 Aug, 21:08, "Alexander Nickolov" <agnicko...@xxxxxxxx> wrote:
That's the normal case and I imagine 99% of the socket code
out there uses no specialflags.
Still it is strange to require magic numbers as default.
I too have a hard time figuring out what it is suppose to offer.
In my (Perl) program recv hangs until it have read as many bytes as
specified by the third arg.
As I understand the documentation that is the behavior if MSG_WAITALL
is set.
But I have set the 'flag' 0, which means ???
I just wanna read until oef on the socket. How do I do that?
Best regards!
.
- Follow-Ups:
- Re: the 4th parameter of 'recv' function, 0?
- From: Luke Alcatel
- Re: the 4th parameter of 'recv' function, 0?
- References:
- the 4th parameter of 'recv' function, 0?
- From: Alex
- Re: the 4th parameter of 'recv' function, 0?
- From: Alexander Nickolov
- the 4th parameter of 'recv' function, 0?
- Prev by Date: Re: First UDP message to a specific IP gets lost
- Next by Date: Timing problems with MailSlots
- Previous by thread: Re: the 4th parameter of 'recv' function, 0?
- Next by thread: Re: the 4th parameter of 'recv' function, 0?
- Index(es):
Loading