Hi Jakub, On Mon, Feb 23, 2015, Jakub Pawlowski wrote: > > Since we can't any more track multiple different discoveries within the > > same application (D-Bus connection) the StopDiscovery behavior is now > > quite broken. The simplest way around that would be to add a discovery > > instance return parameter to StartServiceDiscovery and to have a new > > StopServiceDiscovery D-Bus method that'd take this as an input > > parameter. > > Right now each application can call StartDiscovery only once, I want > each application to be able to call StartDiscovery OR > StartFilteredDiscovery only once. This way we are completly fine with > one StopDiscovery method. If some application needs to change filter, > it can always stop and restart it's scan. Actually I remembered wrong how the current code works. I thought it was allowing multiple StartDiscovery() per app, but there's indeed a hard-coded limit of just one. Keeping this policy around would allow StopDiscovery to be used for StartDiscovery and StartServiceDiscovery alike, and each app would then only be allowed to call one of those at a time. Johan -- 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
