Re: [PATCH 2/2] doc/device-api.txt Information about D-Bus LastSeen property

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

 





On 02.08.2016 18:57, Bastien Nocera wrote:

It's doesn't, really, until you apply heuristics to it. How do you plan
to use this?

Initially, there is a requirement for application to detect if a list of device are available for connection or not. Before connection and after.

As far as I understood, d-bus interface doesn't provide any way to detect if device is advertising or not.

le_seen and bredr_seen provides the last time when device's advertisement packet was detected (Of course if my understanding is correct)

Application can read LastSeen time, read current time and compare with application-defined timeout to make a decision if device is alive.

Yes, this property doesn't answer to direct question "Alive or not". But in this way user can apply any heuristic algorithm he wants.

And this approach doesn't require any BLE connections to device.

--
Best regards,
Andrey Zheregelya

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[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