*Contact emails* [email protected] *Explainer* https://github.com/WebBluetoothCG/web-bluetooth/pull/672
*Specification* https://pr-preview.s3.amazonaws.com/hjanuschka/web-bluetooth/pull/672.html#dom-bluetoothremotegattserver-maxwritewithoutresponsesize *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. implementation: https://chromium-review.googlesource.com/c/chromium/src/+/7879985 Bug: 40265040, 40686244, 40163619 *Blink component* Blink>Bluetooth <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EBluetooth%22> *Web Feature ID* web-bluetooth <https://webstatus.dev/features/web-bluetooth> *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. *Initial public proposal* https://github.com/WebBluetoothCG/web-bluetooth/issues/383 *Goals for experimentation* None *Requires code in //chrome?* False *Tracking bug* https://issues.chromium.org/issues/40265040 *Non-OSS dependencies* Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function? None beyond the platform Bluetooth APIs already used by Chromium's Web Bluetooth implementation: Android BluetoothGatt, CoreBluetooth, WinRT GATT, and BlueZ D-Bus. *Estimated milestones* Shipping on desktop 157 Shipping on Android 157 *Anticipated spec changes* Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). The API shape has converged in WebBluetoothCG PR 672 and the PR is approved. No further substantive changes are anticipated, but the PR must be merged before shipping. *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/5177569273053184?gate=5191492164517888 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFmjHKQ0ftKQn-37UikGJC2Zos%2BGyiOw7%2B5t-nx8NnRTckOUiQ%40mail.gmail.com.
