[GODRIVER-2520] Simplify GridFS timeout API Created: 08/Aug/22 Updated: 14/Nov/23 Resolved: 14/Nov/23 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | GridFS |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benji Rewis (Inactive) | Assignee: | Preston Vasquez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Epic Link: | Go Driver 2.0: Driver | ||||||||||||||||
| Backwards Compatibility: | Major Change | ||||||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Preston Vasquez', 'email': 'prestonvasquez@icloud.com', 'username': 'prestonvasquez'}Message: |