Skip to content
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

Feature Request: Configurable Network Timeout #160

Open
wscheicher opened this issue Mar 28, 2018 · 2 comments
Open

Feature Request: Configurable Network Timeout #160

wscheicher opened this issue Mar 28, 2018 · 2 comments

Comments

@wscheicher
Copy link

wscheicher commented Mar 28, 2018

As far as i understand, Gobby does handle Network interruptions of up to 10 Minutes very well.
After that you have to manually merge your changes.

A lot of users seem to frequently miss the reconnect deadline by a bit in a lot of situations so i would like to increase the Timeout.
So i'm asking: could this be made configurable?
I already searched the sources but couldn't find anything obvious.
What does control this timeout?

@pkern
Copy link
Contributor

pkern commented Mar 28, 2018

As far as I know it just depends on the TCP network connection surviving. If it does and bytes start flowing again, Gobby will catch up. It will not - however - be able to re-sync after the network connection dropped entirely and a reconnect is needed.

@wscheicher
Copy link
Author

Oh.
That explains quite a bit.
And it seems i have to learn about the various layers of a network connection.
Like if the TCP connection timeouts are global or if a application can use different settings for its connections

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

No branches or pull requests

2 participants