#23 file locking

[Brett Wuth]

Implement file locking so that two instances of JPasswords cannot overwrite each other's changes to the database. The file locking should allow the database to reside on a network file system (e.g. SMB) and be accessed from multiple computers.

Use case:

An organization wants to have a centralized JPassword database accessed from different computers.

[Wolfgang Keller]

File locking is implemented with 0-6-0 RC1.
It works, however, not in some famous environments like Linux, as for the missing feature of the OS there. Also it currently works late, that is you can open and modify the database without notice, but you can't save it when conflicting.

[Wolfgang Keller]

Casual file locking, as implemented by some projects, is a nuisance and I refuse to perform such a request because it is to no avail. The salvation JPasswords has taken is to implement the MERGE-ON-CONFLICT feature since 1.1, which allows parallel instances addressing a file - under assumption an operating system of file access would synchronise writing. Otherwise there pertains a rest of risk for which there is no salvation. Hope this helps!