[Bug 237127] kaddressbook looses contact data

adrian at jadic.us adrian at jadic.us
Sun May 16 17:01:41 BST 2010


https://bugs.kde.org/show_bug.cgi?id=237127





--- Comment #5 from  <adrian jadic us>  2010-05-16 18:01:39 ---
I think this solves only part of the problem.

What if I access the filesystem simultaneously with 2 apps. Or if the directory
is shared and my wife accesses it with her laptop.

I would suggest looking into:
1. Manual button in GUI to synchronise with filesystem.

2. If the user opens a contact for editing it should be loaded from the
filesystem (synchronised). This should be done only for that specific contact
to reduce traffic. This would ensure that one user is not editing what another
user already did.

3. Currently, if the user edits a contact and closes the window the vcf file
gets overwritten regardless if it matched or not what was in Akonadi's cache.
Akonadi should notify the user if the vcf file it overwrites is not the same as
was in the cache. (just like Kate does when you open a system file and the
system modifies it after you opened it).

Just an observation:

It appears to me that the "personal contacts" type of resource was only
intended to be used in a unique instance of Akonadi. See the warning file in
the ./local/contacts folder. If it is indeed intended for a single user single
instance then this bug should be addressed in a different manner.
Akonadi should place some sort of lock on the directory, so that no other
Akonadi instance or another app can use it. IDK if this is possible.
But I know that you can't just rely on a text file in a folder to tell users
not to use that kind of resource in a multi-user/instance environment.

If this can't be done then I would just treat all resources the same way
whether they are shared (on the network) or not. This will also eliminate the
current confusion when adding address-books.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list