On Fri, 2009-02-06 at 14:58 -0500, Bill Nottingham wrote:
> David Zeuthen (da...@fubar.dk) said:
> > Also, why this on D-Bus in the first place? Why can't interested parties
> > read /proc themselves? AFAICT, it doesn't require any privileges...
>
> The above statement could be read to apply to battery data too,
> with probably the same answer.
I disagree. The difference here is that reading battery data is
something you want to do all the time and it's relatively well-defined
what a battery or power source is. There's also the fact that we want to
drive things like UPSs from our user space daemon and present the data
using the normal interface. So that's useful.
The main thing, I guess, is that we don't want DeviceKit projects to be
the kitchen sink, we tried that before with HAL and it didn't exactly
work out great. So unless there are really good reasons (for example if
privileges are required) for exposing this functionality via IPC I think
we may want to remove it and make the users (e.g. g-p-m) use the native
kernel interfaces instead.
Because.. there's absolutely no need to abstract some abstraction just
for the sake of abstracting it. Especially not if it makes things go
slower, eat more battery and so on.
David
_______________________________________________
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
