It would be very helpful if the received data from a characteristic change could be on the event as well.
That way, if the value is changing in rapid succession (for example, if a characteristic is used for data transfer, such as the Nordic BLE serial port sample), there's no chance of losing data.
So far, it seems like I haven't lost any data as it stands, but Chrome may just be keeping up. Not reassuring. :) BLE notifications/indications are reliable, so there's no reason to make the upper level API unreliable.
It would be very helpful if the received data from a characteristic change could be on the event as well. That way, if the value is changing in rapid succession (for example, if a characteristic is used for data transfer, such as the Nordic BLE serial port sample), there's no chance of losing data. So far, it seems like I haven't lost any data as it stands, but Chrome may just be keeping up. Not reassuring. :) BLE notifications/indications are reliable, so there's no reason to make the upper level API unreliable.