CK: more paranoia, idle status, and creation-time

William Jon McCann mccann at jhu.edu
Mon Feb 19 07:40:02 PST 2007


Hey Richard,

On 2/15/07, Richard Hughes <hughsient at gmail.com> wrote:
> On Thu, 2007-02-15 at 17:12 -0500, William Jon McCann wrote:
> >     void GetIdle                 (OUT boolean is_idle)
> >     void GetIdleSince        (OUT string iso8601_datetime)
>
> So this is on the ck system bus, right? If so, gnome-power-manager
> should query this before it tries to do it's system idle action, instead
> of watching the screensaver session idle time.

The property change notification is emitted from the CK session
object.  In the case where the session is GNOME related this property
is set by gnome-screensaver.  So, I don't think there is much
advantage to gnome-power-manager not listening to gnome-screensaver
directly.  There are some disadvantages like adding more points of
failure, the fact that this property is not necessarily authoritative
(at the moment anything can use the SetIdle method - not just a
screensaver or presence monitor), and that we don't track the
lifecycle of the caller (don't handle if it calls SetIdle and then
dies).

I suppose it is fair to ask what good is this then.  Well not sure.
It is at least useful as a replacement for "finger" type
functionality.  Which may be used by login managers/user
switchers/presence systems of the future.

Jon


More information about the hal mailing list