blockwise transfer for payloads bigger than RAM size about mbed-client-c HOT 7 CLOSED

FYI @mlnx

from mbed-client-c.

Hi, There is a need for providing possibility for application to provide their own memory blocks to handle this case. It is an extension feature that is planned to be implemented. We haven't yet figured out the complete details, if you have any suggestions that you would like to see , please share and we can take that into consideration.

from mbed-client-c.

I think the handle should have sn_coap_rx_callback_block_chunk() which if set should be called with information about the chunk number, size and payload (possibly also source port and address). The writing of the chunk to flash should block the transmission of further chunks.

Would be good if this could be combined with the LWM2M object for Firmware Update.

from mbed-client-c.

ARM Internal Ref: IOTCLT-729

from mbed-client-c.

Thanks for the suggestion. It makes sense to have an API on Firmware Update class to pass the callback function pointer, as well as add a new API on mbed-client-c to support this feature at both layers.

from mbed-client-c.

mbed client blockwise do not work

from mbed-client-c.

Feature is now available and documentation how it can be used can be found from mbed-client examples and documentation page.
https://docs.mbed.com/docs/mbed-client-guide/en/latest/Howto/#how-to-create-and-configure-resources-and-resource-instances "Setting an external handler for block-wise messages".

from mbed-client-c.