Help¶

When using a blocking socket, the application can in certain situations fail and hang indefinitely if a watchdog timer is not used. Using a non-blocking socket for data transfers can help avoid getting into such a situation, at the cost of failing in situations where a short period of blocking would have sent the data.

Direct dependencies¶

<choice: Socket behavior when sending>

(Includes any dependencies from ifs and menus.)

Kconfig definition¶

At <nRF>/subsys/net/lib/nrf_cloud/Kconfig:70

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:23 → <Zephyr>/modules/Kconfig:6 → <BuildDir>/Kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:25 → <nRF>/subsys/Kconfig:18 → <nRF>/subsys/net/Kconfig:8 → <nRF>/subsys/net/lib/Kconfig:8

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Networking → Application protocols → nRF Cloud library → Socket behavior when sending

config NRF_CLOUD_SEND_NONBLOCKING
    bool "Send data using non-blocking socket"
    depends on <choice: Socket behavior when sending>
    help
      When using a blocking socket, the application can in certain situations
      fail and hang indefinitely if a watchdog timer is not used.
      Using a non-blocking socket for data transfers can help avoid getting
      into such a situation, at the cost of failing in situations where
      a short period of blocking would have sent the data.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)