On May 22, 2013, at 11:51 AM, bert hubert <[email protected]> wrote:
> On Wed, May 22, 2013 at 10:16:50AM -0400, Jared Mauch wrote: >> [without research random musing] >> >> I would imagine you could just modify the source to use SOCK_STREAM >> instead of SOCK_DGRAM unless it uses sendto or recvfrom. It would also > > Setting up a TCP/IP connection in non-blocking fashion is very different > from doing UDP. TCP/IP also comes with the possibility of getting partial > writes, especially under benchmarking conditions, which requires buffering > and keeping state. > > For this reason, none of the UDP-based tools has "just enabled" TCP/IP, we > would've if it were straightforward. It's not *that* hard to write a socket based application to do these types of things, esp for a lab environment where you're not seeing weird variable latency and RTT values for your TCP session. You're just testing the two TCP stacks and the application layer interaction with them. - Jared _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
