You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea for the Stash and Cache card widget is to offer a search functionality that will display results sorted by domain, and allows to interact with the cache (and stash) data that is stored in the Stealth Profile.
Currently, these things are a bit unclear on what's the best way to implement it. In order to have the same level of functionality per-domain AND per-URL, the metadata and external resources of a URL have to be stored in a database that is updated once a URL is re-downloaded or re-optimized.
So it would make sense to have a server-side service that keeps track of metadata of URLs, including all urls that are related to each other (given it is easy to implement and doesn't blow up complexity).
It might make sense here to differ between Pages and Assets in general. Pages are URLs that the user visited and browsed to specifically, whereas Assets are external resources that are necessary to display the Page, given the Site Mode. This would imply that a change of a Site Mode triggers a refresh call in the Browser UI and leads to the recursive metadata update of a Page.
In order to prevent a recursive update scenario that never ends, it might make sense to limit the dependency chain and set the first-level of the dependency graph to be a Page (aka text mode type) or a directly downloaded Asset (aka other mode type).
The text was updated successfully, but these errors were encountered:
The
stealth:history
page needs to be implemented.The idea for the
Stash
andCache
card widget is to offer a search functionality that will display results sorted by domain, and allows to interact with the cache (and stash) data that is stored in the Stealth Profile.Currently, these things are a bit unclear on what's the best way to implement it. In order to have the same level of functionality per-domain AND per-URL, the metadata and external resources of a URL have to be stored in a database that is updated once a URL is re-downloaded or re-optimized.
So it would make sense to have a server-side service that keeps track of metadata of URLs, including all urls that are related to each other (given it is easy to implement and doesn't blow up complexity).
It might make sense here to differ between
Pages
andAssets
in general. Pages are URLs that the user visited and browsed to specifically, whereas Assets are external resources that are necessary to display the Page, given the Site Mode. This would imply that a change of a Site Mode triggers arefresh
call in the Browser UI and leads to the recursive metadata update of a Page.In order to prevent a recursive update scenario that never ends, it might make sense to limit the dependency chain and set the first-level of the dependency graph to be a Page (aka text mode type) or a directly downloaded Asset (aka other mode type).
The text was updated successfully, but these errors were encountered: