Advanced Users can post their questions and comments here for the not so Newbie crowd.
davydnorris wrote:The new MQTT code uses setsockoptions() to set up a receive time out and then select() to enable it - I think I'll just have to hack the existing library at the moment but it's apparently working fine in the RTOS SDK
I am afraid the ones that make the code calling setsockopt() and select() have a bit too much confidence in the level of compatibility regarding LWIP against a full blown Unix IP stack. I wouldn't bet my money on it that it completely works as expected. I think the model of callbacks suits small memory devices much better than select/poll/unix sockets API.
For now, I've converted the higher level new MQTT from RTOS to NonOS, and have started creating an espconn based transport to get me over the line.
I'll go back and look at the lwIP/mbedTLS based code once I get these damn boxes out
What's your experience with mbedtls? I've never used it (never need it...). Is it easy to use on top of an existing LWIP implementation or does it need changes in LWIP? What's the memory footprint (my greatest concern)?