Enhanced Functionality During Connection Setup and Teardown
The
WSAAccept function lets an application obtain caller information such as caller ID and
QOS before deciding whether to accept an incoming connection request. This is
done with a callback to an application-supplied condition function.
User-to-user data specified by parameters in the
WSAConnect function and the condition function of
WSAAccept can be transferred to the peer during connection establishment, provided this
feature is supported by the service provider.
It is also possible (for protocols that support this) to exchange user data
between the endpoints at connection teardown time. The end that initiates the
teardown can call the
WSASendDisconnect function to indicate that no more data be sent and to initiate the connection
teardown sequence. For certain protocols, part of this teardown sequence is
the delivery of disconnect data from the teardown initiator. After receiving
notice that the remote end has initiated the teardown sequence (typically by the
FD_CLOSE indication), the
WSARecvDisconnect function can be called to receive the disconnect data, if any.
To illustrate how disconnect data can be used, consider the following
scenario. The client half of a client/server application is responsible for terminating
a socket connection. Coincident with the termination, it provides (using
disconnect data) the total number of transactions it processed with the server. The
server in turn responds with the cumulative total of transactions that it has
processed with all clients. The sequence of calls and indications might occur as
follows:
Client Side
| Server Side
|
(1) Invoke WSASendDisconnect to conclude session and supply transaction total
|
|
| (2) Get FD_CLOSE, recv with a return value of zero, or WSAEDISCON error return from WSARecv indicating graceful shutdown in progress
|
| (3) Invoke WSARecvDisconnect to get client's transaction total
|
| (4) Compute cumulative grand total of all transactions
|
| (5) Invoke WSASendDisconnect to transmit grand total
|
(6) Receive FD_CLOSE indication
| (5a) Invoke closesocket
|
(7) Invoke WSARecvDisconnect to receive and store cumulative grand total of transactions
|
|
(8) Invoke closesocket
|
|
Note that step (5a) must follow step (5), but has no timing relationship with
step (6), (7), or (8).
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database