https://devzone.nordicsemi.com/f/nordic-q-a/12486/write-without-response-client-exampleI&#39;m writing the client-side code for the Nordic DFU service and according to the spec, the DFU packet characteristic uses Write Without Request. Are there any examples of client code for services that use Write Without Request? Particularly, I&#39;m havingen-USTelligent Community 13Fri, 11 Mar 2016 10:22:51 GMThttps://devzone.nordicsemi.com/thread/47304?ContentTypeID=1Fri, 11 Mar 2016 10:22:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5321b6e3-1b25-4a72-9fe4-d6d633ddab65Anders Strand<p>The <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v11.0.0/ble_sdk_app_nus_c.html?cp=4_0_0_4_2_0_3">NUS central</a> example in our SDK (SDK10 and newer) uses write without request (write command). See inside the <code>ble_nus_c_string_send</code> function in ble_nus_c.c.</p> <p>If your hardware <a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v11.0.0%2Fble_sdk_app_nus_c.html&amp;cp=4_0_0_4_2_0_3">supports</a> it i recommend using the newest SDK and softdevice.</p> <p>I understand that the part about the buffers is confusing. It is actually about internal buffer in the softdevice, and is not something the user needs to think about. The main difference between the two is that the write command does not need an application level acknowledgement before sending the next packet. It can send a lot of packets each connection interval, while a write request can only send one packet each interval. This is because the peripheral must approve the request before a new one can be sent. This approval can be done the earliest on the next connection interval.</p> <p>The write command offers better throughput, and that is why it is used in applications where you send a lot of data (like in OTA DFU).</p> <p>-Anders</p><div style="clear:both;"></div>