Re: Solaris 8 network programming problem
- From: Casper H.S. Dik <Casper.Dik@xxxxxxx>
- Date: 14 Nov 2006 10:21:19 GMT
James Antill <james-netnews@xxxxxxx> writes:
read/recv returning 0 on a socket means the other end has shutdown(), and
so there is no more data.
Or a 0 length message was received (non-SOCK_STREAM transports only)
Which is better read or recv ?
It doesn't matter in POSIX, although sometimes it's useful to use recv()
to imply to a programmer that the interface is expecting a socket and
read() to imply that it could be a network socket or a file.
read(2) is at liberty to concatenate UDP messages; recv(2) is not.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
.
- Follow-Ups:
- Re: Solaris 8 network programming problem
- From: James Carlson
- Re: Solaris 8 network programming problem
- From: sansp00
- Re: Solaris 8 network programming problem
- From: Rainer Weikusat
- Re: Solaris 8 network programming problem
- References:
- Solaris 8 network programming problem
- From: sansp00
- Re: Solaris 8 network programming problem
- From: Maxim Yegorushkin
- Re: Solaris 8 network programming problem
- From: sansp00
- Re: Solaris 8 network programming problem
- From: James Antill
- Re: Solaris 8 network programming problem
- From: sansp00
- Re: Solaris 8 network programming problem
- From: James Antill
- Solaris 8 network programming problem
- Prev by Date: Re: about visit "com" port
- Next by Date: Re: to select() or poll() ??
- Previous by thread: Re: Solaris 8 network programming problem
- Next by thread: Re: Solaris 8 network programming problem
- Index(es):
Relevant Pages
|