Jon Shallow 069a0786ce CSM: Support different XMT and RCV Max-Message-Size ...

Track the RCV mtu size separately from the XMT mtu, so that sufficiently
large PDUs can be built for receiving incoming data.

Wait until reliable session is complete and the initial CSM have been exchanged
before building any new PDUs for transmission so that they can hold the
appropriate amount of Max-Message-Size data.

Add in support into coap-server and coap-client for defining the
Max-Message-Size to use by adding in 2 new functions
coap_context_set_csm_max_message_size() and
coap_context_get_csm_max_message_size().

Add in flexibility into coap-server to control the initial example_data size.

Requires #844 to prevent recursive mutex locking when initiating proxy ongoing
session to upstream server.

2022-05-04 10:01:37 +01:00

..

coap3

CSM: Support different XMT and RCV Max-Message-Size

2022-05-04 10:01:37 +01:00