Fix socketTimeoutMS spec compliance

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • 3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Needed
    • None
    • C Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      The spec dictates the following behavior for socketTimeoutMS:

      • If socketTimeoutMS is not specified, the default is no timeout.
      • socketTimeoutMS=0 means no timeout.

      The C Driver does not conform to this. Instead, the C Driver behaves as follows:

      • The default is 5 minutes.
      • socketTimeoutMS=0 is ignored due to CDRIVER-3730, in which case the default (5 minutes) is used.
      • socketTimeoutMS=inf means no timeout. This is a stopgap measure introduced by CDRIVER-5815 to avoid a breaking change.

      Provided socketTimeoutMS is not supplanted by CSOT's timeoutMS by the time we are ready to release version 3, we should fix the C Driver's handling of socketTimeoutMS to be spec-compliant.

            Assignee:
            Unassigned
            Reporter:
            Connor MacDonald
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: