KWalletD syncing

[Aaron J. Seigo]

On Thursday 12 June 2008, Michael Leupold wrote:
> I've prepared a small patch to add syncing on every change. Unfortunately
> it makes the wallet be synced 3 times on creating a new one. What do you
> think?

usually what i do in such situations is move the syncing to a slot and then 
call that slot with either a zero timer (so as soon as the event loop gets hit 
again) or a reasonably short timeout[1] from the places that a sync should be 
triggered.

that way if multiple syncs get called in a row (or, at least, within the 
timeout period) you get just one sync instead of repeated syncs.

btw, have you tested the performance impact of this with large wallets?

[1] what "reasonably short" means is very much up to the exact application 
being considered.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080612/9b0b49e5/attachment.sig>