-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
In MongoClientSettings TimeSpan.Infinite means no timeout according to .Net conventions
While in ConnectionString 0 denotes no timeout according to spec.
Seems that for each setting, handling of 0 and Infinite is done differently and in a different area. Ideally we need a single place to convert spec standards to .Net convention.
- is related to
-
CSHARP-3138 Define behavior of connectTimeoutMS=0 with streaming protocol
- Backlog