Communication protocol handler for the taskrambler framework. This does not contain specific protocol implementations but the abstract code to handle them.

taskrambler

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: d32d05f52e

1.0.0

master

v1.0.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'd32d05f52e'

${ noResults }

libtrcomm/testers

History

Georg Hopp d32d05f52e Revert "try for a threaded server, but not very much luck now." This reverts commit c0b33ec777.		11 years ago
..
build.sh	build separate client for udp	11 years ago
test_handler.c	Make the raw protocol to a real protocol. It sends the message size now before the message. This was neccessary because after I activated optimization in gcc the testclient was always only reading 2 bytes in the initial successfull read.	11 years ago
test_handler.h	show some information about the bytes per second throughput. Currently I manage around 1.1 GBytes on a loopback device which sounds not to bad, but is only about 1/4 of the throughput iperf shows me... but this might be related to nc... I will see this when I have written my own client.	11 years ago
testclient.c	build separate client for udp	11 years ago
testclient.sh	show some information about the bytes per second throughput. Currently I manage around 1.1 GBytes on a loopback device which sounds not to bad, but is only about 1/4 of the throughput iperf shows me... but this might be related to nc... I will see this when I have written my own client.	11 years ago
testserver.c	fix close handling and introduce server class	11 years ago
testserver2.c	fix some memory leaks	11 years ago