Hi Emil, On Sat, Feb 29, 2020 at 2:13 AM Emil Lenngren <emil.lenngren@xxxxxxxxx> wrote: > > Hi. I have a feature request that the negotiated ATT MTU should be > exposed as a property in the org.bluez.Device1 interface. > > For some applications it's good to know or required how much data that > can be written / read / notified in each packet, and it's not always > desired or possible to use AcquireNotify / AcquireWrite. We already negotiate a fairly big MTU maximum by default, and you can just use AcquireWrite/AcquireNotify just to discover it and the close the fd immediately, so I suppose we cover much of what the feature is, except perhaps if the application requires something bellow the default MTU bluetoothd but that can be a problem if other application would start requiring their own MTU as well, so even if we introduce a Property that would have to be read-only but there may be races if the application start writing/reading too fast or the remote end do trigger its own exchange for some reason. -- Luiz Augusto von Dentz
