Hi,
On Tue, Jul 25, 2017 at 8:14 PM, Christopher Collins <ch...@runtime.io> wrote: > On Tue, Jul 25, 2017 at 10:46:32AM -0700, Pritish Gandhi wrote: > [...] > [...] > > Is this true for notifications too? If I need to send notifications for > > that long characteristic value, will my access callback be called several > > times based on the MTU of the connection? > > Unfortunately, Bluetooth restricts notifications to a single packet. If > the characteristic value is longer than the MTU allows, the notification > gets truncated. To get around this, the application needs to chunk the > value into several notifications, and possibly use some protocol which > indicates the total length, parts remaining, etc. > Also client can just do long read in order to read remaining portion of characteristic value - this is what ATT spec suggests. It depends on actual use case, but this way client may be able to decide whether it should read remaining portion of value or skip it, e.g. some flags can be placed at the beginning of the characteristic value and they will be always sent in notification. Best regards, Andrzej
