Message: previous - next
Month: August 2013

tdehwlib upower and devicekit-power backend

From: Slávek Banko <slavek.banko@...>
Date: Tue, 13 Aug 2013 01:10:33 +0200

as pointed out by François in bug report 1588, upower was previously named 
devicekit-power. And with corresponding dbus paths.

I wonder what is the cost of dbus call? I hesitate to support devicekit-power 
as an second dbus paths for upower or as a standalone backend.

What is your opinion?