[GODRIVER-814] Make Topology, Server, and Connection configuration public Created: 06/Feb/19  Updated: 27/Oct/23  Resolved: 13/May/19

Status: Closed
Project: Go Driver
Component/s: Options & Configuration
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kristofer Brandow (Inactive) Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by GODRIVER-793 Remove all public use of 'x' packages... Closed
Epic Link: Core API

 Description   

Configuring a topology.Topology, topology.Server, or connection.Connection currently requires using self referential functions, but the parameters to these options are themselves functions to enable adaptive changing of settings. While this is a useful design for complex configuration scenarios, the configuration of these types is simple. Additionally, since the configuration types are all private, it is extremely difficult to test if they have been correctly setup.

Remove the current way options are configured for the topology.Topology, topology.Server, and connection.Connection types and make their configuration types public. This configuration should operate in the same manner as the options for mongo.Client and other similar types.



 Comments   
Comment by Kristofer Brandow (Inactive) [ 13/May/19 ]

After writing mongo.Client.configure this isn't as necessary and we get some benefit from creating a new configuration instance every time we instantiate a Topology, Server, or connection.

Generated at Thu Feb 08 08:35:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.