[DRIVERS-722] Cursor spec Created: 19/Aug/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Esha Bhargava Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45775 responseTo does not match requestId f... Closed
is related to DRIVERS-2176 Create Cursor Specification Backlog

 Description   

Cursors are a fundamental part of every driver's API, yet they may have differing behavior between drivers because their behavior is largely unspecified. This is surprising and confusing for users who expect that the core behavior and API of drivers are similar across languages.

Additionally, in async environments, drivers gain the ability to cheaply run tasks in the background, and this may allow for new cursor behavior and capabilities that are currently unexplored. The usage patterns of cursors and expectations of their API are notably different in async than they are in sync environments, and those expectations and usage patterns should be codified in the specifications. Exhaust cursors are incoming and also affect the capabilities, usage patterns, and API expectations of cursors, all of which should be specified as well.


Generated at Thu Feb 08 08:22:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.