Multiperipheral Queued Writes - a buffer for each connection means a lot of space required. Can I deny simultaneous writes?https://devzone.nordicsemi.com/f/nordic-q-a/37342/multiperipheral-queued-writes---a-buffer-for-each-connection-means-a-lot-of-space-required-can-i-deny-simultaneous-writesI&#39;m currently adding a large characteristic (5.3 times bigger than my max MTU) to my device that supports multiple peripheral connections. This characteristic is used to set up/change a stored config on the device and so, will be written to seldomly buten-USTelligent Community 13Thu, 16 Aug 2018 14:10:54 GMTRE: Multiperipheral Queued Writes - a buffer for each connection means a lot of space required. Can I deny simultaneous writes?https://devzone.nordicsemi.com/thread/144570?ContentTypeID=1Thu, 16 Aug 2018 14:10:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6a008886-04e8-4108-8daa-acf4f75c9a0fbjorn-spockeli<p>Hi Goldwake,&nbsp;</p> <p>If you do not want to allocate more than one buffer at the time , then you could keep track of the number of&nbsp;BLE_EVT_USER_MEM_REQUEST and&nbsp;BLE_EVT_USER_MEM_RELEASE events you receive. So when you receive the first BLE_EVT_USER_MEM_REQUEST, then you do not reply with&nbsp;sd_ble_user_mem_reply() for subsequent&nbsp;BLE_EVT_USER_MEM_REQUEST events until you receive&nbsp;BLE_EVT_USER_MEM_RELEASE corresponding to the first BLE_EVT_USER_MEM_REQUEST.</p> <p>There is no such thing as a long notification, the size of an attribute value(i.e the characteristic value) that is notified is limited to&nbsp;0 to (ATT_MTU-3).&nbsp;If the attribute value is longer than (ATT_MTU-3) octets, then only the first(ATT_MTU-3) octets of this attributes value can be sent in a notification, see&nbsp;BLUETOOTH SPECIFICATION Version 5.0 | Vol 3, Part F, Section 3.4.7.1</p> <p>Best regards</p> <p>Bjørn&nbsp;</p><div style="clear:both;"></div>