callout on property change

[David Zeuthen]

On Tue, 2004-04-20 at 19:35, Robert Love wrote:
> Heh, funny example - I thought the same thing to myself, "well, I guess
> we can never do statistics such as network card tx/rx".  I concluded the
> same, that maybe such stats are overkill.  Keeping the HAL database
> relatively stable, in the sense that a somewhat idle system does not
> involve a lot of property changes, seems right.
> 

I very much agree; note that at some point we'll also need all the
properties on disk (so we don't have to go through .fdi-file scanning at
every hald startup) and we really don't want to spin up the disks all
the time.

> I really like the current callout scheme, for its simplicity.
> 

Heh :-) Actually the only callout we're missing right now is
DeviceCondtion, e.g. the signal used to report a condition on a device
which cannot easily be expressed in a device property - for example to
say "Processor is overheating" (not implemented yet) or "This volume was
unmounted" (actually implemented; hald lazy unmount volumes for devices
the (bad) user yanks out without unmounting them).

It's funny; with lshal, hal-set-property and callouts you can pretty
much, if you want to that is, emulate the network API we today provide
through D-BUS :-)

Cheers,
David


_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal