On Thu, February 20, 2014 20:03:20 Aaron J. Seigo wrote: > Either a better solution needs to be found for KDBusConnectionPool or a > warning should be placed prominently in the apidox about this “gotcha” and > perhaps it should be completely avoided in other frameworks where it is > impossible to know the threading model of the application that will be using > it. Or, I suppose, we could invent a policy that applications should do all > dbus related activities in a specific thread .. though that can be > difficult to know as dbus calls are often hidden within libraries.
An apidox warning at the very least sounds appropriate. On a less related note, all this talk about threading models is starting to remind me of a bunch of Microsoft COM programmers talking about "apartment models" and such from 10 years ago. I'm also starting to think that all of our DBus interfaces intended for general programmatic consumption need to be async; I've been able to encounter the most amazing deadlocks sometimes. Of course this is both hard to do and hard to train/teach others to know how to do. :-/ Regards, - Michael Pyne _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
