Hi Marcel, On 31 May 2014 07:17, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Andrzej, > >> This patch introduces API to monitor connection parameters. >> >> New device properties are introduced: ConnectionRSSI, ConnectionTXPower >> and ConnectionTXPowerMax. >> >> Client can request to poll for updates of RSSI and TX power via Start- >> and StopConnectionMonitor methods. > > I am not convinced on the naming of the method calls and properties. They feel complicated and long and not really clear with its purpose. > > What I am curious if we just expose the calculated pathloss or some value that has a more clear sense and usefulness for proximity. Why not do the job for the application instead of letting the application figure it out by itself. For pathloss you'll need remote TX power so it could be done from PXP which has (or can have) this value. But still, on BR/EDR pathloss is kind of useless due to how RSSI is defined. What if we move these properties to new interface (and perhaps implement in plugin), something like let's say org.bluez.Connection1? And mark it as experimental for now, let's see how it works. BR, Andrzej -- 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
