HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man2/!!!intro.2
________________________________________________________________
___ ___
s
send(2) send(2)
guarantee delivery. Sending large messages may cause too many fragments and overrun a receiver’s abil-
ity to receive them. If this happens the complete message cannot be reassembled. This affects the
apparent reliabilityand throughput of the network as viewed by the end user.
The default and maximum buffer sizes are protocol-specific. Refer to the appropriate entries in Sections 7F
and 7P for details. The buffer size can be set by calling setsockopt() with SO_SNDBUF.
AF_CCITT
If the receiving process is on a Series 700/800 HP-UX system, and the connection has been set up to use the
D-bit, data sent with the D-bit set is acknowledged when the receiving process has read the data. Other-
wise, the acknowledgement is sent when the firmware receives it.
OBSOLESCENCE
Currently, the socklen_t and size_t types are the same size. This is compatible with both the UNIX
95 and UNIX 98 profiles. However, in a future release, socklen_t might be a different size. In that
case, the size of the msghdr and cmsghdr structures and the relative position of their members will be
different, which might affect application behavior. Applications that use socklen_t now, where
appropriate, will avoid such migration problems. On the other hand, applications that need to be portable
to the UNIX 95 profile should follow the X/Open specification (see xopen_networking(7)).
FUTURE DIRECTION
Currently, the default behavior is the HP-UX BSD Sockets; however, it might be changed to X/Open
Sockets in a future release. At that time, any HP-UX BSD Sockets behavior that is incompatible with
X/Open Sockets might be obsoleted. Applications that conform to the X/Open specification now will avoid
migration problems (see xopen_networking(7)).
MULTITHREAD USAGE
The
send(), sendmsg(), and sendto() system calls are thread-safe. They each have a cancellation
point; and they are async-cancel safe, async-signalsafe, and fork-safe.
AUTHOR
send(), sendmsg(), and sendto() were developed by HP and the University of California, Berkeley.
SEE ALSO
ifconfig(1M), getsockopt(2), recv(2), select(2), setsockopt(2), socket(2), socket(7), socketx25(7), af_ccitt(7F),
af_vme_link(7F), inet(7F), tcp(7P), udp(7P), unix(7P), xopen_networking(7).
STANDARDS CONFORMANCE
send(): XPG4
HP-UX Release 11i: December 2000 − 6 − Section 2−−299
___
___