13 | | At run-time Tmix "replays" the exchanges encoded in the set of connection vectors. Tmix is simultaneously run on two machines, each at the edge of a test network. One machine plays the role of initiator, while the other is the acceptor. For each connection vector a TCP connection is established from the initiator to the acceptor at time ''T,,i,,''. The initiator then performs socket writes to send ''a,,1,,'' bytes (the size of the ADU of epoch 1) of fake data. At the same time, Tmix on the acceptor reads the same number of bytes from it's associated socket. The roles then reverse with the acceptor sending a "response" of ''b,,1,,'' bytes back to the initiator, while it reads them. The initiator then sleeps for ''t,,i,,'' seconds before sending the next "request". The last epoch of a connection doesn't contain a "think" time, and when it is reached the connection is terminated. |
| 13 | At run-time Tmix "replays" the exchanges encoded in the set of connection vectors. Tmix is simultaneously run on two machines, each at the edge of a test network. One machine plays the role of initiator, while the other is the acceptor. For each connection vector a TCP connection is established from the initiator to the acceptor at time ''T,,i,,''. The initiator then performs socket writes to send ''a,,1,,'' bytes (the size of the "request" ADU of epoch 1) of fake data. At the same time, Tmix on the acceptor reads the same number of bytes from it's associated socket. The roles then reverse with the acceptor sending a "response" of ''b,,1,,'' bytes back to the initiator, while it reads them. The initiator then sleeps for ''t,,i,,'' seconds before sending the next "request". The last epoch of a connection doesn't contain a "think" time, and when it is reached the connection is terminated. |