Lines Matching refs:attempts

420 …ally attempts to reconnect or retry connection after connection loss or failure, the connectivity …
424 …* If the underlying technology automatically attempts to reconnect after losing connection, and pe…
429 *Technologiess that give up on connection attempts*
432 If the underlying technology has no mechanism to retry connection attempts, or would give up on the…
434 * If your underlying technology is not persistent, you must manually trigger reconnect attempts whe…
435 …hnology does not support a timeout, you must manually cancel connection attempts if the timeout is…
436 …technology forces a timeout, you must manually trigger a new connection attempts if that timeout i…
445 Instead, these underlying technologies may need to make multiple back-to-back association attempts …
447 …implementation should treat this series of back-to-back association sub-attempts as a single unifi…
449 …empt failure, persistence being disabled should not prevent further sub-attempts, since they all c…
452 At which point a series of failed sub-attempts should be considered a failure of the connection att…
454 …t the configured timeout has not yet elapsed, or there is no timeout, sub-attempts should continue.
458 *Persistence during connection attempts*
462 Persistence should only affect whether or not connection attempts are automatically triggered after…