Björn Lichtblau

Useless is a bit far fetched, as gauravgh said you can always have an outer catch-all exception handler in your processRecords and then exit on your own to destroy the...

Need to check this more closely but looks like it would need switching/porting to `IotNetworkInterface_t`. Currently not yet fully understood how new `IotNetworkInterface_t` is to be used vs the `SOCKETS_...

Indeed, you are right. But that `_networkReceiveTask` -> `_destroyConnection` -> `SOCKETS_Close` after getting an error from `SOCKETS_Recv` only happens if `destroyConnection` had been set ( https://github.com/aws/amazon-freertos/blob/master/libraries/abstractions/platform/freertos/iot_network_freertos.c#L202 ), and that depends...

Hi, I just bumped our code to using the new IotMqtt_xxx v2 API. I am still seeing that behaviour that an underlying SOCKETS_Recv returning an error stops the NetRecv thread,...

> Follow the spec This [has recently been called out](https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0123.html) as commonly misinterpreted > FTR, this is a common misinterpretation, but that is not what it says and > certainly...

> Follow the spec This [has recently been called out](https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0123.html) as commonly misinterpreted > FTR, this is a common misinterpretation, but that is not what it says and > certainly...