Skip to content

WIP: Handle keepalive missing events #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 13 commits into
base: tcp_server
Choose a base branch
from
Draft

Conversation

fmauch
Copy link
Owner

@fmauch fmauch commented Mar 24, 2021

This will disconnect the ReverseInterface when keepalive signals are missing.

The problem with this implementation is that pausing the program on the robot
will also trigger this.

fmauch added 13 commits March 15, 2021 14:36
This implements an event-based tcp server for easier use. It is
decoupled from the TCPSocket class to remove one layer of complexity.

Also, the event-based approach allows interrupting this server as it
won't be blocking inside an accept or recv call if not applicable.
- Updated documentation
- Removed (unused) setSocketFD method
This will disconnect the ReverseInterface when keepalive signals are missing.

The problem with this implementation is that pausing the program on the robot
will also trigger this.
@fmauch
Copy link
Owner Author

fmauch commented Mar 24, 2021

In the back of my head I remember facing this problem in the past.

So, this would be by intention that (missing) keepalive signal handling is not being done currently.

@fmauch
Copy link
Owner Author

fmauch commented Mar 24, 2021

Maybe a better approach would be to use the SO_KEEPALIVE socket option.

@fmauch fmauch force-pushed the tcp_server branch 3 times, most recently from 4a286db to ed16661 Compare March 26, 2021 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant