Issue 583 (#586)

* s/bandwidth/bitrate/ in user-facing places.  Towards #583.

iperf3 has long misused terminology; bandwidth is a measure of
capacity.  iperf3 measures bitrate or throughput.  We standardize
on "bitrate" because it begins with the same letter as "bandwidth"
(to match the -b command-line option).

User-facing output mentioning "bandwidth" now uses "bitrate".
The long command-line option for -b (--bandwidth) is now --bitrate
(--bandwidth is transparently accepted for backward compatibility).
A few places in documentation that talk about bandwidth as a
measured value have been reworded to use bitrate or throughput.

There are a number of places in code where variables are still
called "bandwidth".  We leave these alone for now.

A mention of "bandwidth" in the test parameters JSON also needs
to remain unchanged to avoid breaking compatibility.  However,
the test results JSON never used the term "bandwidth" in
the first place.

* s/bandwidth/throughput in one place in RPM description.  Towards #583.

1 files changed, 1 insertions, 1 deletions

diff --git a/iperf3.spec.in b/iperf3.spec.in
index 8d89c8b..f2f1573 100644
--- a/iperf3.spec.in
+++ b/iperf3.spec.in
@@ -19,7 +19,7 @@ BuildRequires: openssl-devel
 iperf3 is a tool for active measurements of the maximum achievable
 bandwidth between two IP hosts.  It supports tuning of various
 parameters related to timing, protocols, and buffers.  For each test,
-it reports the bandwidth, loss, and other parameters.
+it reports the throughput, loss, and other parameters.
 
 %package        devel
 Summary:        Development files for %{name}