DAST: Iperf - Request a pull versus push data transfer direction flag - BrookeP1 --at-- aol.com
>Date: Thu, 8 Sep 2005 13:36:50 -0500
>To: BrookeP1 --at-- aol.com
>Subject: DAST: Iperf - Request a pull versus push data transfer direction
flag - BrookeP1 --at-- aol.com
>
>Contacting DAST re: Feature request about Iperf
>From: Brooke Patterson <BrookeP1 --at-- aol.com>
>
>Subject: Request a pull versus push data transfer direction flag
>
>Question/Comment:
>Iperf TCP testing seems to work under the model that the client makes a
TCP connection and pushes down data to the server.
>
>The dualtest flag tells the client to open a listen socket and the data is
pushed by the client and pushed by the server.
>
>I would like to request a flag that tells the client to do pulls instead
of pushes. So the client would still initiate the TCP connection, but then
the server would send the data up to the client.
>
>Why is this useful? HTTP connections are pulls, not pushes. I am testing a
configuration in which firewall concerns prevent a dualtest type test from
working. The direction in which the TCP connection is allowed, is the
opposite of the direction of data flow.
>
>I looked at the iperf source (2.0.2), but the change is beyond my
non-existant C and C++ skills.
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
Project: http://dast.nlanr.net | Personal: http://hobbes.ncsa.uiuc.edu