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
Implement resource locking #5687
Comments
The issue here is to decide when to remove the lock. We don't know when will be the last edit (depending on the external editor application). |
Some basic work has started in 87590c6e6c91fae576ff998d5dc39e12a89daf47 in Sardine. |
Hi, just wondering of which ticket this one is a duplicate ? |
Regarding unlocking, I would say, timeout by default reissued if file is still in edition and a button to "try" an unlock arbitrarily) |
Replying to [comment:6 Joseph Piron]:
If implemented that would need to be transparent to the user. |
Replying to [comment:5 Joseph Piron]:
No problem about a duplicate. The next step would be to overload all methods in the Sardine interface that need lock support to accept an additional lock parameter. |
Last week I sent the following question to support@mountainduck.io:
Today, David Kocher replied with the following:
So as requested I am now doing so. One simple option is to simply provide toolbar or menu functions to lock and unlock a file manually as a separate process from editing a file. While it is not as automated as automatically locking and unlocking a file while editing it, it at least exposes the functionality in a way that can be used. |
Upstream work in c3acbdd977ccaa3d41dd085923524c898952688c. |
Though locking is one of the four core operations mentioned by the WebDAV RFC (the other three being properties, collections and namespace operations), Cyberduck doesn’t yet implement it.
https://tools.ietf.org/html/rfc2518#section-6
The text was updated successfully, but these errors were encountered: