Cache Data Used in Cancel Scan to use with following Post Scan
When performing a cancel scan, data for each item is gathered. This data could be cached to use for the subsequent post scan (if the post scan were to occur within a specific time frame). This would speed up the cancel/post routine.
This use of cached data could be turned on or off via a user setting in the event that a user wants live data for the post regardless of when the cancel scan happened.
With all the optimizations for scan speed, this wouldn’t be possible.
Zoran Hranj commented
This is exactly the idea I wanted to post just now :)
Can this idea be revived and maybe reconsidered, now that TSM4 is out?