Socket Connection Test Module
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The socket connection test module, Wsx_bind.exe, uses multiple threads to create connections, exchange a small amount of data over them, and then tear down the connections. This test module exercises the Winsock layer, the underlying Winsock providers, and the networking stack. You can run this test module on both Internet Protocol version 6 (IPv6) and Internet Protocol version 4 (IPv4).
To maximize the thoroughness of the test module, you can set up the test module across a client and a server. The test module acts as the client, initiating all actions. The server acts only as an echo service, accepting data from the client and echoing back the data verbatim on the same connection. On the server, you can use Echosrv.exe from a command prompt to perform this action, by using a command such as echosrv -p12678.
The following table shows the command line parameters for the Wsx_bind.exe test module.
| Parameter | Description |
|---|---|
-w |
Time to wait between binds, in milliseconds. You can use this option to reduce the chance that multiple, concurrent bind tests interfere with one another. You can also use this option to prevent the test module from cycling through ports too quickly. |
-t |
Number of concurrent threads to use. |
-p |
Port with which to connect. |
This test module resolves the server name specified by the -server option for the Windows Embedded CE Stress tool harness. The test module also resolves the address of the target. In the command line for the harness, if you do not specify a value for the -server option, the default value of localhost instructs this test module to use the local computer name as the target. For more information, see Options for the Windows Embedded CE Stress Tool.