Hi Alex, > This fix implements a new GetCachedServices() function with similar > functionality as DiscoverServices(), except it only retrieves information > from an internal cache. > > Signed-off-by: Alex Deymo <deymo@xxxxxxxxxxxx> > > --- > > Some background: > Currently, only the device properties are always available while the device > is off or out of range, but the service records are not. The > org.bluez.Device.ServiceRecords() call fails if the device is off, but some > important information relevant to the connection is present only there. For > example, for mice and keyboard, the HIDNormallyConnectable and > HIDReconnectInitiate tells if we are supposed to initiate a connection to > the device while it is off. When bluetoothd restarts and has such a divice > paired in its records, there is no way from the DBus interface to tell if > this device is "normally connectable" or not. This GetCachedServices() aims > to solve this problem. why would we expose this in this format and not make the HID support work according to these SDP attributes? Just make it work without having any application interact with it. Or on a different questions, why are these not exported as properties for the input interface. Why this big hammer one fits all approach? Regards Marcel -- 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
