Hi Luiz,
--------------------------------------------------
From: "Luiz Augusto von Dentz" <luiz.dentz@xxxxxxxxx>
Sent: Friday, November 23, 2012 3:24 PM
To: "Jaganath" <jaganath.k@xxxxxxxxxxx>
Cc: <linux-bluetooth@xxxxxxxxxxxxxxx>
Subject: Re: Query regarding device discovery
Hi,
On Fri, Nov 23, 2012 at 11:27 AM, JAGANATH KANAKKASSERY
<jaganath.k@xxxxxxxxxxx> wrote:
Hello,
I have a doubt with current discovery mechanism.
Suppose application 1 calls "StartDiscovery". for which "Discovering =
TRUE" comes
and then deviceFound signals starts coming.
In the mean time application 2 calls "StartDiscovery" which will be
queued in BlueZ.
Then "discovering = FALSE" comes for the discovery initiated from
application 1.
Then as per BlueZ design, it will restart discovery for application 1
since it has not
called "StopDiscovery" yet. So "discovering = TRUE" comes again, which
application 2
thinks that it belongs to him.
Then if application 1 calls "StopDiscovery" immediately, discovery will
be stopped
and "Discovering = FALSE" comes with which application 2 too thinks that
discovery
initiated by him is also done.
So eventually application 2 will not get any devices.
So I think with current design, applications that are interested only in
one complete
inquiry session will be in trouble.
So can we disable the automatic reinitiating of device discovery?
Or is there any way to handle this scenario?
StartDiscovery doesn't queue the sessions, it actually increase the
reference to the same discovery session which became shared between
the callers, it should not interfere with the ongoing discovery nor
change how we emit Discovering. That being said the concept of one
shot inquiry is flawed since it can miss devices, with addition of LE
this is even more visible because each inquiry is only 5.12 sec., you
can still detect when an inquiry is active just check when Discovering
is TRUE and nope it should not matter if there is 1 or 20 application
listening to it once Discovery switch to TRUE we are inquiring/scan
when it switch to FALSE it has stopped and is probably doing name
resolving.
With this concept even if inquiry is completed, Discovery = FALSE should not
be sent. Because anyway BlueZ will start a new Discovery on its own.
So application gets Discovery = FALSE and then immediately Discovery = TRUE.
So I think until application calls "StopDiscovery", Discovery = FALSE should
not be sent
Thanks,
Jaganath
--
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
