However, the developers later decided that this interaction is not important for most apps, thus, they have been removed from the final CB stack.
Well, you had it right up to this point - I'm not sure who told you that :)
Simply put, these APIs were pulled because we could not find a good way to fulfill the spirit of the contract that they represent. On a peripheral device with an abstracted GATT database being shared among multiple applications, the concept of providing useful "connection" notifications isn't as cut and dry as you might think.
Ultimately, we decided that the the majority of use-cases could still be achieved via the other CBPeripherlManagerDelegate methods, so we decided to not implement the connect/disconnect events. As always, if you have a use-case that isn't doable with the current API and/or policy, please let us know by filing a bug.
On Jun 10, 2013, at 3:14 AM, András Kövi <
email@hidden> wrote:
Hi Fred,
there used to be callbacks on the peripheral manager for this purpose, they are actually mentioned in the WWDC2012 presentations. However, the developers later decided that this interaction is not important for most apps, thus, they have been removed from the final CB stack.
You can register the clients in the subscribe and unsubscribe callbacks and this in for is also available if there is a write request or read for a dynamic attribute. This is all you have at the moment.
Andras