Re: [RFC BlueZ 0/2] Fix types and names of beacon/import flags.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Michal,

On Tue, 2020-01-21 at 21:15 +0100, Michał Lowas-Rzechonek wrote:
> Hi Brian, Inga,
> 
> On 01/09, Michał Lowas-Rzechonek wrote:
> > This patchset aims to make the API a bit more consistent.
> > 
> > Side question: at the moment none of the node properties emit
> > PropertiesChanged signal. I think this violates D-Bus spec, since all
> > properties are assumed to emit these signals by default [1] [2].
> > 
> > Unfortunately, at the moment ELL does not support "EmitsChangedSignal"
> > annotation, so I'd like to add this to ELL, annotate node
> > properties with:
> >     - Features: const
> >     - Beacon: true
> >     - BeaconFlags: true
> >     - IvIndex: true
> >     - SecondsSinceLastHeard: false (for performance reasons)
> >     - Addresses: const
> > 
> > And also emit PropertiesChanged where required.
> > 
> > Thoughts?
> 
> Any comments about this idea, or should I just go ahead and send a
> patch?
> 

I think this is a good idea. I agree with the proposed node properties
annotations.

Thanks,
Inga




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux