← Back to release summary

Web Bluetooth: BluetoothRemoteGATTServer.maxWriteWithoutResponseSize

Category
Miscellaneous
Type
New or changed feature
Status
Proposed (Chrome Proposed)
Intent stage
None

Summary

Adds BluetoothRemoteGATTServer.maxWriteWithoutResponseSize, which reports the largest payload that writeValueWithoutResponse() can send in one ATT packet. A maxwritewithoutresponsesizechanged event notifies applications when Chrome observes the value change, allowing applications to size chunks without assuming a 20-byte limit. it depends on: https://chromestatus.com/feature/5138797158334464 and will be shipped together. implementation: https://chromium-review.googlesource.com/c/chromium/src/+/7879985 Bug: 40265040, 40686244, 40163619

Motivation

Web Bluetooth applications currently cannot determine the largest payload accepted by writeValueWithoutResponse() for an active GATT connection. They must hard-code the 20-byte default, use platform-specific heuristics, or probe with writes and handle platform-dependent failures or truncation. Exposing the usable payload size allows applications to chunk transfers correctly and use larger ATT MTUs for substantially better throughput.

Standards & signals

Ecosystem

Samples: https://static.januschka.com/i-40265040

Explainers: https://github.com/WebBluetoothCG/web-bluetooth/pull/672

View on chromestatus.com