[GODRIVER-66] Implement unacknowledged writes with async goroutines Created: 16/Aug/17 Updated: 28/Oct/23 Resolved: 21/Nov/17 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | CRUD |
| Affects Version/s: | None |
| Fix Version/s: | 0.0.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Samuel Rossi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | GODRIVER Core Specs |
| Description |
|
Updated: In order to emulate legacy opcode latency with unacknowledged writes, the driver needs to process the database reply asynchronously in a goroutine before returning the connection to the pool. Originally:
|
| Comments |
| Comment by Githook User [ 27/Nov/17 ] |
|
Author: {'name': 'Saghm Rossi', 'username': 'saghm', 'email': 'saghmrossi@gmail.com'}Message: |
| Comment by Githook User [ 21/Nov/17 ] |
|
Author: {'name': 'Saghm Rossi', 'username': 'saghm', 'email': 'saghmrossi@gmail.com'}Message: |
| Comment by Craig Wilson [ 23/Aug/17 ] |
|
Unacknowledged writes can be implemented with goroutines very easily. I think you should skip implementing legacy opcodes altogether. |
| Comment by Christopher Hendel [ 17/Aug/17 ] |
|
I think we could skip legacy op codes. They are already scheduled for deprecation/removal here. |