[GODRIVER-93] Should we take non-connection string options in Client constructor? Created: 27/Sep/17  Updated: 11/Sep/19  Resolved: 13/Dec/17

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

Type: Task Priority: Major - P3
Reporter: Samuel Rossi (Inactive) Assignee: David Golden
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: GODRIVER Alpha UX

 Description   

Currently, we only accept options to the Client constructor through the connection string. We should decide whether or not to provide the ability to specify options through the constructor outside of the connection string (and if so, whether or not the connection string options should take precedence).



 Comments   
Comment by David Golden [ 13/Dec/17 ]

Based on feedback from driver leads, there seems to be some consensus that allowing non URI based configuration is desirable, even while emphasizing URI configuration.

I think for the alpha release, we should support URI configuration only, and later – before the GA – add a new client constructor that takes an options structure (or variadic options functions) in addition to a URI and resolved their precedence per the connection string spec.

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