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

Dev/205 new client disconnect guard #207

Merged
merged 11 commits into from
Dec 20, 2023

Conversation

smatsson
Copy link
Collaborator

No description provided.

@smatsson smatsson linked an issue Sep 30, 2023 that may be closed by this pull request
@smatsson smatsson modified the milestones: 2.7.1+1, 2.5+1 Nov 2, 2023
@smatsson smatsson force-pushed the dev/205-new-client-disconnect-guard branch 2 times, most recently from 9c46bfa to f239291 Compare November 4, 2023 10:36
@smatsson smatsson force-pushed the dev/205-new-client-disconnect-guard branch from f239291 to cbfddb6 Compare November 11, 2023 19:06
@smatsson smatsson modified the milestones: 2.7.1+1, 2.7.2+1 Nov 17, 2023
This increases stability in cases where data is in transfer but has not yet reached the server when the client disconnects and reconnects. In earlier version this would cause the wrong offset to be retrieved. The client would continue from that offset causing an error when trying to patch the data once the lock had been released (offset mismatch).

Response code for locked operations have been changed from 409 Conflict to 423 Locked to better conform to how clients and other servers are implemented.
@smatsson smatsson marked this pull request as ready for review December 20, 2023 13:50
@smatsson smatsson merged commit 0d36520 into master Dec 20, 2023
@smatsson smatsson deleted the dev/205-new-client-disconnect-guard branch December 20, 2023 13:51
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.

Rewrite the client discconect guard to support timeouts
1 participant