RFC: blocking DBus calls

[Aaron J. Seigo]

hi... another policy suggestion:

DBus calls made from within classes should always be async calls and not block 
the class unless one of the following conditions is met:

* The class can easily be put into a separate thread, so as not to block the 
host application.

* The DBus call can be guaranteed to take a minimal round trip time ("instant" 
reply gaurantee)

.. this is another one we keep getting hit with in Plasma, krunner and 
elsewhere. usually it's just "lazy" programming and it absolutely destroys 
user interface fluidity, which is more and more important as we move to more 
animated and fluid UIs.

-- 
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 Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20111105/2689be6d/attachment.sig>