Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-2520

Simplify GridFS timeout API

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.0.0
    • Affects Version/s: None
    • Component/s: GridFS
    • None
    • Major Change
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Currently, most GridFS methods do not take contexts as parameters and instead rely on readDeadline and writeDeadline (see here). This is not particularly idiomatic, and the interaction between Timeout, readDeadline/writeDeadline and a context deadline can be quite confusing.

      Ideally, every GridFS method should take a context parameter (whose deadline defaults to one specified by Timeout) and the readDeadline/writeDeadline logic should be removed.

            Assignee:
            preston.vasquez@mongodb.com Preston Vasquez
            Reporter:
            benji.rewis@mongodb.com Benji Rewis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: