HP 800 HP DLPI Programmer's Guide - Page 40

Connection Handoff, accepted using DL_CONNECT_RES. DL_CONNECT_CON informs

Page 40 highlights

Introduction to DLPI DLPI Services Figure 1-12 Normal Connection Establishment In the connection establishment model, the caller initiates connection establishment, while the callee waits for incoming requests. DL_CONNECT_REQ requests that the DLS provider establish a connection. DL_CONNECT_IND informs the callee of the request, which may be accepted using DL_CONNECT_RES. DL_CONNECT_CON informs the caller that the connection has been established. The normal sequence of messages is illustrated in Figure 1-12. Message Flow: Successful Connection Establishment DL_CONNECT request DL_CONNECT indication DL_CONNECT confirm DL_CONNECT response DL_OK acknowledge Once the connection is established, the DLS users may exchange user data using DL_DATA_REQ and DL_DATA_IND. The DLS user may accept an incoming connect request on either the stream where the connect indication arrived or at an alternate, responding stream. The responding stream is indicated by a token in the DL_CONNECT_RES. This token is a value associated with the responding stream and is obtained by issuing a DL_TOKEN_REQ on that stream. The DLS provider responds to this request by generating a token for the stream and returning it to the DLS user in a DL_TOKEN_ACK. Connection Handoff Connections may be established on a stream other than that which received the DL_CONNECT_IND by passing a non-zero dl_resp_token in the DL_CONNECT_RES. The dl_resp_token value is obtained by doing a DL_TOKEN_REQ on the stream to which the connection is being passed (the data stream). The DL_CONNECT_RES is done on the stream which received the DL_CONNECT_IND (the control stream). Both the control and data streams must be bound on the same local SAP. After the DL_CONNECT_RES, the control stream will be left in the 40 Chapter 1

  • 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
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

Introduction to DLPI
DLPI Services
Chapter 1
40
Normal Connection Establishment
In the connection establishment
model, the caller initiates connection establishment, while the callee
waits for incoming requests. DL_CONNECT_REQ requests that the DLS
provider establish a connection.
DL_CONNECT_IND informs the callee of the request, which may be
accepted using DL_CONNECT_RES. DL_CONNECT_CON informs the
caller that the connection has been established.
The normal sequence of messages is illustrated in Figure 1-12.
Figure 1-12
Message Flow: Successful Connection Establishment
Once the connection is established, the DLS users may exchange user
data using DL_DATA_REQ and DL_DATA_IND.
The DLS user may accept an incoming connect request on either the
stream where the connect indication arrived or at an alternate,
responding stream. The responding stream is indicated by a token in the
DL_CONNECT_RES. This token is a value associated with the
responding stream and is obtained by issuing a DL_TOKEN_REQ on
that stream. The DLS provider responds to this request by generating a
token for the stream and returning it to the DLS user in a
DL_TOKEN_ACK.
Connection Handoff
Connections may be established on a stream other than that which
received the DL_CONNECT_IND by passing a non-zero dl_resp_token in
the DL_CONNECT_RES. The dl_resp_token value is obtained by doing a
DL_TOKEN_REQ on the stream to which the connection is being passed
(the data stream). The DL_CONNECT_RES is done on the stream which
received the DL_CONNECT_IND (the control stream). Both the control
and data streams must be bound on the same local SAP. After the
DL_CONNECT_RES, the control stream will be left in the
DL_CONNECT
request
DL_CONNECT
confirm
DL_CONNECT
DL_CONNECT
DL_OK
response
indication
acknowledge