wolfssl

Author	SHA1	Message	Date
Hayden Roche	5fdc4cf6e1	Fix RX/TX throughput reporting in example server. - I observed that client TX throughput < client RX throughput, but server TX throughput > server RX throughput. Turns out this is just a typo in the printing of the stats. The RX stat was being printed as the TX stat and vice- versa. - I added a note to scripts/benchmark.test about a 2 second sleep we do waiting for the server to come up. If you were to time this script with the time command, you'll see that 2 seconds in the result, which might be confusing if you didn't realize the sleep was there.	2020-12-08 16:49:09 -06:00
Eric Blankenhorn	b83804cb9d	Correct misspellings and typos from codespell tool	2019-12-24 12:29:33 -06:00
Michael Shihrer	fa94f5ffe9	Replaced == with -eq to fix benchmark.test scripting error	2016-05-20 09:43:30 -06:00
David Garske	fdab3943be	Added throughput benchmarking for client/server examples and added helper script "scripts/benchmark.test". Added example client option: "-B <num>" Benchmarking throughput. Added example server options: "-B <num>" Benchmark throughput, "-e" Echo data, "-i" Loop / Accept multiple connections. Cleanup of the include.am for examples. Cleanup of tcp_connect with DTLS enabled. Cleanup of the valid socket checking. Cleanup trailing whitespace.	2015-10-14 19:13:45 -07:00