A naive approach of creating a random transaction ID for each fetch. The latest ID, stored in state, will be the expected one -- any other transaction results will be dropped.
The loading spinner will continue to spin until the latest ID's results are fetched.
Sample
Example of 3 fast filter switches:
??
This assumes there's no quick, built-in way to abort dispatched tasks (only did a quick Google search for it). The ability to abort would speed up the wait-time.
Issue
Closes lbry-desktop 4317: Transaction list shows previously requested data / pages
Approach
A naive approach of creating a random transaction ID for each fetch. The latest ID, stored in
state
, will be the expected one -- any other transaction results will be dropped.The loading spinner will continue to spin until the latest ID's results are fetched.
Sample
Example of 3 fast filter switches:
??
This assumes there's no quick, built-in way to abort dispatched tasks (only did a quick Google search for it). The ability to abort would speed up the wait-time.