Thanks for this detailed answer, indeed we will check the WebDAV server.
As for the file opened in read-only mode by default now, I find it a big
change with respect to the former behavior: why such a change?
Thanks,
*NeoDoc*
*Camille Bégnis*
[email protected]
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/
On 16/04/2014 17:54, Hussein Shafie wrote:
On 04/16/2014 04:28 PM, Camille Bégnis wrote:
Hello,
A little request for enhancement when dealing with locked file on a
WebDAV repository.
If the connection fails or XXE hangs, the remote file might remain
locked even though it is actually closed on XXE side.
When the user tries to open it again, XXE tells him that the file is
locked and offers the possibility to open it in read-only, or read-write
mode.
This has slightly changed since v5.8.1 (December 12, 2013). The
document is now always opened in read-only mode, but...see
http://www.xmlmind.com/xmleditor/changes.html#v5.8.1:
---
* Using "File|Save As" to save a document opened in read-only mode now
makes it switch to the normal read-write mode. This new behavior is
deemed to be more intuitive for the user.
---
It would be useful to add a third option if the user is the same that
had isssued the former lock. This option would release and issue the
lock again before opening the file in normal mode.
This is already the case.
1) I've opened a file on a WebDAV server (Apache mod_dav).
2) Killed XXE so the file remains locked.
3) Restarted XXE.
4) I've checked that the file was still locked by me (an exclusive lock).
5) Reopened the locked file and got a dialog box (see attached
screenshot) suggesting exactly what you want.
6) I clicked "Yes" and was able to reacquire the lock on the document.
Please note that:
A) I used XXE v5.9 to run this test. However the behavior you have
described is implemented since XXE v3.
B) I identified myself as a lock owner[*] as "[email protected]".
The WebDAV server was able to keep this information handy and to
return it --as well as the lock token-- to XXE, after XXE was
restarted due to the simulated crash.
Please make sure that this *critical* feature (which is ``full active
lock discovery'') is correctly implemented by the WebDAV server you use.
---
[*] Reference:
* http://www.webdav.org/specs/rfc4918.html#rfc.section.6.8
* http://www.webdav.org/specs/rfc4918.html#ELEMENT_activelock
* http://www.webdav.org/specs/rfc4918.html#ELEMENT_owner
* http://www.webdav.org/specs/rfc4918.html#ELEMENT_locktoken
Thanks,
--
*NeoDoc*
*Camille Bégnis*
[email protected]
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
