[patch] asynchronous callouts

[David Zeuthen]

On Thu, 2004-04-22 at 23:41, Joe Shaw wrote:
> On Tue, 2004-04-20 at 22:45 +0200, David Zeuthen wrote:
> > Ok - thinking a bit more about it, we should probably callout right
> > after merging from .fdi files..
> > 
> > That is, just before adding to the GDL but after the device is named. 
> > 
> > This means our D-BUS access functions also must search the TDL
> > (temporary device list), but this should be an easy fix.
> 
> Ok, I've started on this.

Very nice.

>   Should all of the dbus messages search the
> TDL?  Ie, should Manager.GetAllDevices() also return devices in the TDL?
> What about Manager.FindDeviceStringMatch()?  Or should it only be ones
> that take the UDI as an argument?
> 

Only the ones that take an UDI - the thinking is that the device should
remain 'invisible' but we still need to allow callouts, who know the
device because of the UDI environment variable we've passed, to modify
it. Makes sense?

Cheers,
David


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