Lines Matching full:connection

47     :alt: A detailed view of how Connection Manager integrates with Zephyr and the application.
50     A detailed view of how Connection Manager integrates with Zephyr and the application.
181 Rather than implement all features centrally, Connection Manager relies on each connectivity implem…
183 This approach allows Connection Manager to remain lean, and allows each connectivity implementation…
212 …s should provide means for applications to pre-configure all necessary connection parameters (for …
220 …s because the application pre-configured invalid connection parameters, or did not configure conne…
222 …connectivity implementation should not give up on the connection attempt, even if valid connection…
224 Instead, the connectivity implementation should asynchronously wait for valid connection parameters…
242 …* It is acceptable to gate this behind a small timeout (separate from the connection timeout) for …
284 …for the connectivity implementation to interpret this as an unexpected connection loss and immedia…
293 For instance, calls to :c:member:`conn_mgr_conn_api.connect` should initiate a connection process a…
315 Connection Manager provides a context pointer to each binding.
391 …work management <net_mgmt_interface>` events are not triggered automatically by Connection Manager.
395 Trigger :c:macro:`NET_EVENT_CONN_CMD_IF_TIMEOUT` when a connection :ref:`timeout <conn_mgr_control_…
398 Trigger :c:macro:`NET_EVENT_CONN_IF_FATAL_ERROR` when a fatal (non-recoverable) connection error oc…
420 …rlying technology automatically attempts to reconnect or retry connection after connection loss or…
424 …* If the underlying technology automatically attempts to reconnect after losing connection, and pe…
425 …connection attempt times out on an iface whose underlying technology does not have a built-in time…
429 *Technologiess that give up on connection attempts*
432 …connection attempts, or would give up on them before the user-configured timeout, or would not rec…
435 * If your underlying technology does not support a timeout, you must manually cancel connection att…
436 …a timeout, you must manually trigger a new connection attempts if that timeout is shorter than the…
447 … treat this series of back-to-back association sub-attempts as a single unified connection attempt.
449 …ld not prevent further sub-attempts, since they all count as one single overall connection attempt.
452 At which point a series of failed sub-attempts should be considered a failure of the connection att…
454 If the connection attempt crosses this threshold, but the configured timeout has not yet elapsed, o…
458 *Persistence during connection attempts*
461 Persistence should not affect any aspect of implementation behavior during a connection attempt.
462 …sistence should only affect whether or not connection attempts are automatically triggered after a…
464 The configured timeout should fully determine whether connection retry should be performed.