Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
Security Level: Public
-
None
-
2
Description
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they also have an option in the connstr to override this and explicitly force the network type to be: auto (the default heuristic), default (internal networking), or a named network (e.g. external).
Described here:
https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j
The plan to move off of cbdatasource means this isn't nessesary for Lithium
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to CBSE-9478 [ CBSE-9478 ] |
Description |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they have an option in the connstr to override this and explicitly set internal, external, or auto (the default).
Described here: https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1–NnQIzk/edit# The plan to move off of cbdatasource means this fix isn't nessesary for Lithium |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they have an option in the connstr to override this and explicitly set internal, external, or auto (the default).
Described here: [https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1]–NnQIzk/edit# The plan to move off of cbdatasource means this isn't nessesary for Lithium |
Description |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they have an option in the connstr to override this and explicitly set internal, external, or auto (the default).
Described here: [https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1]–NnQIzk/edit# The plan to move off of cbdatasource means this isn't nessesary for Lithium |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they have an option in the connstr to override this and explicitly set internal, external, or auto (the default).
Described here: [https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j|https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j] The plan to move off of cbdatasource means this isn't nessesary for Lithium |
Description |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they have an option in the connstr to override this and explicitly set internal, external, or auto (the default).
Described here: [https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j|https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j] The plan to move off of cbdatasource means this isn't nessesary for Lithium |
The current heuristic-driven behaviour for selecting internal/external networking matches the default behaviour of SDKs, but they also have an option in the connstr to override this and explicitly force the network type to be: auto (the default heuristic), default (internal networking), or a named network (e.g. external).
Described here: [https://docs.google.com/document/d/1706x2zMsYoBXQ-8H0cpW0KDYpeBy_FZ9dt1--NnQIzk/edit#heading=h.eabhsruer98j] The plan to move off of cbdatasource means this isn't nessesary for Lithium |

Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |