tcpsockets | Example source code from my TCP/IP Network | TCP library

by vichargrave C++ Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | tcpsockets Summary

tcpsockets is a C++ library typically used in Networking, TCP applications. tcpsockets has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Example source code from my TCP/IP Network Programming Design Patterns in C++ and TCP/IP Sockets with Time Out Capabilities blogs.

Support

Quality

Security

License

Reuse

Support

tcpsockets has a low active ecosystem.

It has 156 star(s) with 82 fork(s). There are 23 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 4 have been closed. On average issues are closed in 151 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of tcpsockets is current.

Quality

tcpsockets has 0 bugs and 0 code smells.

Security

tcpsockets has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

tcpsockets code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

tcpsockets does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

tcpsockets releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of tcpsockets

Get all kandi verified functions for this library.

tcpsockets Key Features

No Key Features are available at this moment for tcpsockets.

tcpsockets Examples and Code Snippets

No Code Snippets are available at this moment for tcpsockets.

Community Discussions

Trending Discussions on tcpsockets

TCP sender machine receiver-window-size shrinking to 0 on windows machine after sending tiny amounts of data for a few minutes

QUESTION

TCP sender machine receiver-window-size shrinking to 0 on windows machine after sending tiny amounts of data for a few minutes

Asked 2020-Nov-22 at 05:23

I'm writing an app that works on a windows laptop that sends TCP bytes in a loop as a "homemade keep-alive" message to keep a connection active (the server machine will disconnect after 15 seconds of no TCP data received). The "server machine" will send the laptop small chunks of data (about .5K bytes/second) as long as a connection is alive (according to the server documentation, this is ideally this is an "echo" packet, but I was unable to find how this is accomplished in .NET). My problem is that when I view this data in Wireshark I can see good network activity, then, after a few minutes, the "win" (receive window size available on the laptop) shrinks from 65K to 0 in increments of about 240 bytes each packet. Why is this happening and how can I prevent it? I can't seem to get the "keep-alive" flags in .Net to work, so this was supposed to be my workaround. I do not see any missed ACK messages, and my data rate is about 2Kb/sec, so I don't understand why the laptop window size is dropping. I definitely assume there is a misconception on my part about TCP and or windows/.NET use of TCPsockets since I have no experience with TCP (I've always used UDP).

...

ANSWER

Answered 2020-Nov-21 at 22:21

You should really be familiar with RFC 793, Transmission Control Protocol, which is the definition of TCP. It explains the wondow and how it is used for flow control:

Flow Control:

TCP provides a means for the receiver to govern the amount of data sent by the sender. This is achieved by returning a "window" with every ACK indicating a range of acceptable sequence numbers beyond the last segment successfully received. The window indicates an allowed number of octets that the sender may transmit before receiving further permission.

-and-

To govern the flow of data between TCPs, a flow control mechanism is employed. The receiving TCP reports a "window" to the sending TCP. This window specifies the number of octets, starting with the acknowledgment number, that the receiving TCP is currently prepared to receive.

-and-

Window: 16 bits

The number of data octets beginning with the one indicated in the acknowledgment field which the sender of this segment is willing to accept.

The window size is dictated by the receiver of the data in its ACK segments where it acknowledges receipt of the data. If your laptop receive window shrinks to 0, it is setting the window to that because it has no more space to receive, and it needs time to process and free up space in the receive buffer. When it has more space, it will send an ACK segment with a larger window.

Source https://stackoverflow.com/questions/64940751

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install tcpsockets

cd to the tcpsockets directory.
Type make to build all the clients and servers

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: