If my case use two iDevices, one in central and one as peripheral, how can I make sure the connection disconnected immediately?
You can't guarantee that, and shouldn't rely on it. By it's nature, the multi-process architecture of iOS means that there may be another application running who still wants that connection up, even if you don't.
On Jan 29, 2013, at 9:49 AM, Khaos Tian < email@hidden> wrote: Thanks for your remind :)
So you suggest that the most reliable way to cause a physical disconnection immediately is to initiate it from the peripheral side. If my case use two iDevices, one in central and one as peripheral, how can I make sure the connection disconnected immediately? As what I knew there isn't possible to initiate cancel connection on CBPeripheralManager side.
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|