You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
By defining lazy-deployment to be TRUE or FALSE, Pathfinder will deploy all fallback paths' operators at initialisation or at their activation, respectively.
Here, pathfinder will first deploy the operators of path $step2a. Only if a fault in that path is detected, the operators of path $step2b are deployed and actively used.
The text was updated successfully, but these errors were encountered:
By defining lazy-deployment to be TRUE or FALSE, Pathfinder will deploy all fallback paths' operators at initialisation or at their activation, respectively.
Example:
here, Pathfinder will deploy all operators in the paths $step2a and $step2b at topology initialisation time.
Here, pathfinder will first deploy the operators of path $step2a. Only if a fault in that path is detected, the operators of path $step2b are deployed and actively used.
The text was updated successfully, but these errors were encountered: