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

Using Internet Datagram Sockets

Page 86 highlights

Using Internet Datagram Sockets Overview Overview Internet UDP datagram sockets provide bidirectional flow of data with record boundaries preserved. However, messages are not guaranteed to be reliably delivered. If a message is delivered, there is no guarantee that it is in sequence and unduplicated, but the data in the message are guaranteed to be intact. Datagram sockets allow you to send and receive messages without establishing a connection. Each message includes a destination address. Processes involved in data transfer are not required to have a client-server relationship; the processes can be symmetrical. Unlike stream sockets, datagram sockets allow you to send to many destinations from one socket, and receive from many sources with one socket. There is no two-process model, although a two-process model is the simplest case of a more general multiprocess model. The terms server and client are used in this chapter only in the application sense. There is no difference in the calls that must be made by the processes involved in the data transfer. For example, you might have a name server process that receives host names from clients all over a network. That server process can send host name and internet address combinations back to the clients. This can all be done with one UDP socket. The simplest two-process case is used in this chapter to describe BSD Sockets using datagram sockets. The following table lists the steps involved in exchanging data between datagram sockets. 86 Chapter 4

  • 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

86
Chapter 4
Using Internet Datagram Sockets
Overview
Overview
Internet UDP datagram sockets provide bidirectional flow of data with
record boundaries preserved. However, messages are not guaranteed to
be reliably delivered. If a message is delivered, there is no guarantee
that it is in sequence and unduplicated, but the data in the message are
guaranteed to be intact.
Datagram sockets allow you to send and receive messages
without
establishing a connection. Each message includes a destination
address. Processes involved in data transfer are not required to have a
client-server relationship; the processes can be symmetrical.
Unlike stream sockets, datagram sockets allow you to send to many
destinations from one socket, and receive from many sources with one
socket. There is no two-process model, although a two-process model is
the simplest case of a more general multiprocess model. The terms
server
and
client
are used in this chapter only in the application sense.
There is no difference in the calls that must be made by the processes
involved in the data transfer.
For example, you might have a name server process that receives host
names from clients all over a network. That server process can send host
name and internet address combinations back to the clients. This can all
be done with one UDP socket.
The simplest two-process case is used in this chapter to describe BSD
Sockets using datagram sockets.
The following table lists the steps involved in exchanging data between
datagram sockets.