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

Introduction

Page 17 highlights

BSD Sockets Concepts Introduction Introduction This guide describes the steps involved in establishing and using BSD Sockets connections. It also describes the protocols you must use and how the BSD Sockets system calls interact. The details of each system call are described in the corresponding man pages. Key Terms and Concepts For a basic understanding of BSD Sockets and its general model, you should review the following terms and definitions. address family addressing association The address format used to interpret addresses specified in socket operations. The internet address family (AF_INET) and the Berkeley UNIX Domain address family (AF_UNIX) are supported. A means of labeling a socket so that it is distinguishable from other sockets on a host. A BSD Sockets connection is defined by an association. An AF_INET association contains the (protocol, local address, local port, remote address, remote port)-tuple. An AF_UNIX association contains the (protocol, local address, peer address)-tuple. Associations must be unique; duplicate associations on the same host cannot exist. The tuple is created when the local and remote socket addresses are bound and connected. This means that the association is created in two steps, and there is a chance that two potential associations could be alike between steps. The host prevents duplicate associations by checking for uniqueness of the tuple at connection time, and reporting an error if the tuple is not unique. Chapter 1 17

  • 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
17
BSD Sockets Concepts
Introduction
Introduction
This guide describes the steps involved in establishing and using BSD
Sockets
connections. It also describes the protocols you must use and
how the BSD Sockets system calls interact. The details of each system
call are described in the corresponding man pages.
Key Terms and Concepts
For a basic understanding of BSD Sockets and its general model, you
should review the following terms and definitions.
address family
The address format used to interpret addresses
specified in socket operations. The internet address
family (AF_INET) and the Berkeley UNIX Domain
address family (AF_UNIX) are supported.
addressing
A means of labeling a socket so that it is
distinguishable from other sockets on a host.
association
A BSD Sockets connection is defined by an
association. An AF_INET association contains the
(protocol, local address, local port, remote address,
remote port)-tuple. An AF_UNIX association
contains the (protocol, local address, peer
address)-tuple. Associations must be
unique
;
duplicate associations on the same host cannot
exist. The tuple is created when the local and
remote socket addresses are bound and connected.
This means that the association is created in two
steps, and there is a chance that two potential
associations could be alike between steps. The host
prevents duplicate associations by checking for
uniqueness of the tuple at connection time, and
reporting an error if the tuple is not unique.