Cache Adapter V2 #618
Description
The goal is to create a new cache implementation to replace the old one and allow the cache to live in the local system or in the browser (using LocalStorage API).
What are the responsibilities of this cache?
- Saving settings (flags and warnings to be ignored, theme etc..)
- Saving scanned payloads
- Saving UI states (such as open payloads)
These are mainly used in the CLI and UI.
Payload
We need to store additional metadata for each payloads:
- The timestamp of original scan request
- The timestamp of the last read usage
Payload must be identified by their integrity (feature coming with version 8 of scanner).
UI Changes
- The payload cache is not more associated with the list of packages in the network. We will only take the initial package (or those marked as opened) now.
- Cached payloads now only appears in the Search View (sorted in the order of last read usage).