You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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
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?
The text was updated successfully, but these errors were encountered: