Holger Macht wrote: > The problem is that we have to adjust all clients to use the new > defines(kpowersave, wmpowersave, testclient, dbus_testclient). But I also > think that this is the last chance to do it.
This is no problem IMO > 2. Broadcast everything and always over the bus > ----------------------------------------------- > > Due to the fact we are using DBus now, we do not need a connected client > to send out events, progress, whatever. So we can broadcast everything > (all five MODES) over the bus. Clients still have to connect to take work > off from powersaved. For instance taking care about screenlocking. But > also without a connected client, all messages go over the bus. This is also ok for me, i don't think the overhead should be too high, otherwise DBus is broken by design ;-) -- Stefan Seyfried \ "I didn't want to write for pay. I QA / R&D Team Mobile Devices \ wanted to be paid for what I write." SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen _______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
