Tian’s got it right on all counts. When a device connects, we don’t have any idea what service(s) it’s interested in. So, in order to be safe, we’d have to wake up every app with a CBPeripheralManager, in case it’s the “right” one. This is incredibly wasteful from a power perspective and fairly inelegant to boot.
In the end, it seemed natural that if an app is hosting a service, it could wait to find out about a remote device once it began “using” the service, via a read, write, or subscription event. On Feb 5, 2015, at 12:35 PM, Justin Cooper < email@hidden> wrote:
Thanks for the history and information, Tian!
It does make sense, I suppose...
Justin
|