- From: David Lechner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Sep 2021 21:16:56 +0000
- To: public-web-bluetooth-log@w3.org
An interesting question brought up in the BlueZ issue is "should the MTU value be per-device or per-attribute"? The feature most people are requesting is "I want the MTU that is negotiated when the device connects", but the argument was made that with Bluetooth 5.2 Enhanced Attribute Protocol (EATT), it might make more sense to have a per-attribute property (and that this could even be different for tx vs rx). -- GitHub Notification of comment by dlech Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/383#issuecomment-923316028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 September 2021 21:16:58 UTC