funworks

I agree with the principle. Regarding the Port number, we enforce the client to use the same Address and Port always to maintain its identity, otherwise it is a new...

So, could it be a requirement on libcoap to provide a mechanism to stop CLIENT sending de-register on session close ? Do you think this is a valid use case...

We have addressed the design challenge you have mentioned above in the following manner: We use a lifetime for each observe request being sent from Client to Server. Server maintains...

So, could it be a requirement on libcoap to provide a mechanism to stop CLIENT sending de-register on session close ? Do you think this is a valid use case...

Version: I had taken code from "develop" branch about 3-4 months back(approx.), right after the "mbedtls" support came in. ### **How I am doing concurrent operations:** I have TWO threads....

> @fun-works Can this be closed now? Yes. It works well with increaded nstart value. Thank you so much for the support.

Ok, So I have updated to latest libcoap now. And I am trying to build with FreeRTOS with: ``` #define NO_SYS 0 #define SYS_FREERTOS 1 ``` And I am getting...

well, I added the line: ``` #define COAP_MUTEX_DEFINE(_name) \ static sys_mutex_t _name ``` @coap_mutex_internal.h:63 and it is successful. But I have some other errors now. But I think mutex is...

> Thanks for your help troubleshooting here. > > > But I think mutex is is missing on libcoap for now and you need to fix that. > > #1181...

Btw, is there any plan to have a release with all these lwip changes ? And is it possible to provide cmake support as well for lwip ?