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
Would it make sense to have a NetworkCostPolicy? The options would be "never use high cost networks", "use high cost if lower cost not available", and "use high cost freely (ignore cost)". This would affect gathering, checking, and selecting.
The text was updated successfully, but these errors were encountered:
@pthatcherg Could this issue be addressed via an extended gather policy? "never use" would translate to a policy of not gathering from "high cost" networks. "use high cost if lower cost not available" would translate to trickling lower cost candidates first, seeing if a successful candidate pair is found, and if not, then trickling higher cost candidates. Ignoring cost would imply gathering from both low and high cost networks.
Would it make sense to have a NetworkCostPolicy? The options would be "never use high cost networks", "use high cost if lower cost not available", and "use high cost freely (ignore cost)". This would affect gathering, checking, and selecting.
The text was updated successfully, but these errors were encountered: