09-25-2013 09:50 PM
If I establish a WebDAV connection to Nuxeo, and then edit a file in MS Word 2007, the file shows as 'locked' on the website. However, if I establish the connection via Nuxeo Drive, and edit the file in MS Word, it does NOT show as locked. It would seem desirable to lock the file, regardless of the specific connection type. And it seems like Nuxeo Drive, as an installed application, would be the 'more capable' connection method.
FYI- I'm using super current on everything except MS Word. I downloaded the Nuxeo VMWare image about 2 days ago, and I've customized nothing.
09-26-2013 08:01 AM
Hello,
It's an interesting point you got there. Indeed such behaviour is not implemented in Drive because we have no way, for now, to detect that a file is opened by an application such as MSOffice. In the case of WebDAV, this is native: editing a doc with MSOffice locks it a the file system level (marking it as readonly), this event is detected by the WebDAV client which sends the lock command to the server. In the case of Drive, we don't have a file system notification mechanism (we only look for local changes every 5 seconds) which would be the only way to be informed that a doc has been locked by an application to then be able to call the lock operation on the server. This need is partially tracked by https://jira.nuxeo.com/browse/NXP-9583 which has not been scheduled yet.
Note that the file system locking depends on the OS / file system / program, so in any case this behaviour could not be guaranteed in 100% of the cases, but in the standard one (Windows / MSOffice) it would work.
In any case, Drive handles conflicts so possible concurrent edition should not be blocking.
Finally, setting aside the technical aspect, this is a functional choice which doesn't necessarily fit every use case, so this feature would be an option.
09-26-2013 08:01 AM
Hello,
It's an interesting point you got there. Indeed such behaviour is not implemented in Drive because we have no way, for now, to detect that a file is opened by an application such as MSOffice. In the case of WebDAV, this is native: editing a doc with MSOffice locks it a the file system level (marking it as readonly), this event is detected by the WebDAV client which sends the lock command to the server. In the case of Drive, we don't have a file system notification mechanism (we only look for local changes every 5 seconds) which would be the only way to be informed that a doc has been locked by an application to then be able to call the lock operation on the server. This need is partially tracked by https://jira.nuxeo.com/browse/NXP-9583 which has not been scheduled yet.
Note that the file system locking depends on the OS / file system / program, so in any case this behaviour could not be guaranteed in 100% of the cases, but in the standard one (Windows / MSOffice) it would work.
In any case, Drive handles conflicts so possible concurrent edition should not be blocking.
Finally, setting aside the technical aspect, this is a functional choice which doesn't necessarily fit every use case, so this feature would be an option.
09-26-2013 02:32 PM
Wow that is an awesome answer.
09-26-2013 06:42 PM
Interesting. I'll just add my two cents
09-27-2013 10:17 AM
Thanks for the pointers to mirall and csync, we'll definitively have a look.
09-27-2013 12:59 PM
If you really want server-side locking semantics vs. Nuxeo Drive concurrent edition conflict management, you might consider using the alternative Nuxeo CMIS interface which is now natively supported by MS Office, LibreOffice, etc.
01-30-2017 12:18 PM
Alfresco (I used that system before Nuxeo) uses the Sharepoint protocol for what they call "Direct Edit", might also be a way to go.
12-02-2017 02:16 PM
[bledii](https
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.