Just some output:
Samstag, 1. April 2017
Freitag, 5. August 2016
QDBus is an easier way to interact with DBus then using dbus-send. There is also a GUI qdbusviewer that might help finding and executing stuff. But qdbus and grep seem to be a bit better at that for me.
Executing qdbus will show all services that you can talk to via dbus. Given a servicename it will print possible paths and sub-paths. And when a path is also appended then it will print out methods and signals which can be called or registered to. The output will include the names and types of parameters and the return-type.
Samstag, 27. Februar 2016
Donnerstag, 31. Dezember 2015
A system test I wrote does many requests on a local server. The responses take from some to many seconds to arrive. IO-bound. I thought I should use threads for each request. All requests could start at the same time and when the results are in they could be evaluated.
It worked. Lots of threads were created, did their work and died.
To many threads - one would say.
A threadpool should be a better way...