HP Rp7410 BSD Sockets Interface Programmer's Guide - Page 19

socket address, socket, descriptor, UNIX Domain, Protocol

Page 19 highlights

BSD Sockets Concepts Introduction socket address socket descriptor TCP UDP UNIX Domain Protocol For the internet address family (AF_INET), the socket address consists of the internet address, port address and address family of a socket. The internet and port address combination allows the network to locate a socket. For UNIX Domain (AF_UNIX), the socket address is the directory pathname bound to the socket. A socket descriptor is an HP-UX file descriptor that references a socket instead of an ordinary file. Therefore, it can be used for reading, writing, or most standard file system calls after a BSD Sockets connection is established. System calls that use file descriptors (e.g. read, write, select) can be used with socket descriptors. All BSD Sockets functions use socket descriptors as arguments. Provides the underlying communication support for stream sockets. The Transmission Control Protocol (TCP) is used to implement reliable, sequenced, flow-controlled two-way communication based on byte streams similar to pipes. Refer to the tcp(7p) man page for more information on TCP. Provides the underlying communication support for datagram sockets. The User Datagram Protocol (UDP) is an unreliable protocol. A process receiving messages on a datagram socket could find messages are duplicated, out-of-sequence, or missing. Messages retain their record boundaries and are sent as individually addressed packets. There is no concept of a connection between the communicating sockets. Refer to the udp(7p) man page for more information on UDP. In addition, the UNIX Domain protocol may be used with AF_UNIX sockets for interprocess communication on the same node. Refer to the unix(7p) man page for more information on the UNIX Domain protocol. Chapter 1 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

Chapter 1
19
BSD Sockets Concepts
Introduction
socket address
For the internet address family (AF_INET), the
socket address consists of the internet address, port
address and address family of a socket. The internet
and port address combination allows the network to
locate a socket. For UNIX Domain (AF_UNIX), the
socket address is the directory pathname bound to
the socket.
socket
descriptor
A socket descriptor is an HP-UX file descriptor that
references a socket instead of an ordinary file.
Therefore, it can be used for reading, writing, or
most standard file system calls after a BSD Sockets
connection is established. System calls that use file
descriptors (e.g.
read
,
write
,
select
) can be used
with socket descriptors. All BSD Sockets functions
use socket descriptors as arguments.
TCP
Provides the underlying communication support for
stream sockets. The Transmission Control Protocol
(TCP) is used to implement reliable, sequenced,
flow-controlled two-way communication based on
byte streams similar to pipes. Refer to the
tcp(7p)
man page for more information on TCP.
UDP
Provides the underlying communication support for
datagram sockets. The User Datagram Protocol
(UDP) is an unreliable protocol. A process receiving
messages on a datagram socket could find messages
are duplicated, out-of-sequence, or missing.
Messages retain their record boundaries and are
sent as individually addressed packets. There is no
concept of a connection between the communicating
sockets. Refer to the
udp(7p)
man page for more
information on UDP.
UNIX Domain
Protocol
In addition, the UNIX Domain protocol may be used
with AF_UNIX sockets for interprocess
communication on the same node. Refer to the
unix(7p)
man page for more information on the
UNIX Domain protocol.