-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
The current configuration approach varies:
- Some configuration options may only be set in the URI; e.g. sockettimeoutms
- Some configuration options may only be set via code; e.g. SSL options
- Some configuration options may be set either way: e.g. appname, minimum pool size
Do you have a sense for which of these models will be more common in the future?
Do you expect that options for a pool will always remain a superset of the options for a client?
- is depended on by
-
CXX-1009 mongocxx::pool should take options::pool, not options::ssl
- Closed