Network folder caching
Use cases
When exploring a remote location (in my case a Samba filesystem) I frequently open a folder, see that what I'm looking for is not there, and go back up to check other folders. Every time I go back the contents are fetched again which takes more than 10 seconds, making the process extremely slow.
Desired behavior
The contents are extremely likely to remain unchanged, so they should be cached and shown instantly. New contents can be requested either manually via F5. Alternatively, they can be requested automatically and replace the cached contents when the request completes (although this could result in an issue of the user clicking right after the new contents are shown and going down a wrong folder if contents did change).
Benefits of the solution
Exploring network shares over a slow connection stops being a torture becomes twice as fast, and more, depending on the user's folder access pattern.
Possible drawbacks
New contents for cached folders are not shown right away. However, if the user expects the contents to change, they can use F5 manually.