@dkocher commented

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).

@dkocher commented

Some basic work has started in 87590c6e6c91fae576ff998d5dc39e12a89daf47 in Sardine.

@dkocher commented

#5687 closed as duplicate.

b22d385 commented

Hi, just wondering of which ticket this one is a duplicate ?
Sorry for my duplicate anyway (#6104), this feature is really a must have for my team to use cyberduck and I'd be happy to help implement.

b22d385 commented

Regarding unlocking, I would say, timeout by default reissued if file is still in edition and a button to "try" an unlock arbitrarily)

@dkocher commented

#6104 closed as duplicate.

@dkocher commented

Replying to [comment:6 Joseph Piron]:

Regarding unlocking, I would say, timeout by default reissued if file is still in edition and a button to "try" an unlock arbitrarily)

If implemented that would need to be transparent to the user.

@dkocher commented

Replying to [comment:5 Joseph Piron]:

Hi, just wondering of which ticket this one is a duplicate ?
Sorry for my duplicate anyway (#6104), this feature is really a must have for my team to use cyberduck and I'd be happy to help implement.

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.

a4e08d7 commented

Last week I sent the following question to support@mountainduck.io:

We are in the process of rolling out WebDAV support for developers using our CMS. As I explored the available options for WebDAV clients on both Windows and MacOS platforms, I stumbled across CyberDuck and your new Mountain Duck product. For collaborative development, however, the ability to lock files while you are editing them is critical, and virtually no WebDAV clients currently support locking that we've been able to find. We're especially looking for appropriate tools for our Mac users, since we haven't found any tools they can use to lock and unlock files on a WebDAV share while they are working on them. Are there any plans to support locking files on a WebDAV share in either your CyberDuck or Mountain Duck products?''

Today, David Kocher replied with the following:

Thanks for your interest in Mountain Duck! We do not currently support resource locking as there were implementation issues in Cyberduck with potential dangling locks after editing a file. In Mountain Duck this could be implemented properly I suppose. Please reopen and comment ticket [1] to allow us track the issue.''

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.

@dkocher commented

Upstream work in c3acbdd977ccaa3d41dd085923524c898952688c.

@dkocher commented

More in a7dedeb.