W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > January 2018

[web-bluetooth] API which provides the negotiated MTU is required

From: Martin Woolley via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Jan 2018 09:39:34 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issues.opened-291141245-1516786773-sysbot+gh@w3.org>
bluetooth-mdw has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth:

== API which provides the negotiated MTU is required ==
Bluetooth mesh runs over Bluetooth LE and defines a proxy node and associated proxy protocol to allow standard (non-mesh) Bluetooth LE clients to talk to a mesh network. 

The proxy protocol requires you to know the MTU which was negotiated behind the scenes by client and server so that packets can be filled and segmentation used when messages exceed the size of the MTU. MTU negotiation happens silently behind the scenes in Web Bluetooth and there's no API that lets you find out what the outcome of that negotiation was. This is needed for the reasons given. Please consider adding an API such as getNeogitatedMTU(). 

Thanks

Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/383 using your GitHub account
Received on Wednesday, 24 January 2018 09:39:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 24 January 2018 09:39:37 UTC