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
When hosting a JupyterLite page, there is a balance between avoiding user data loss (by having a persistent storage backend) and not having independent sessions interfere (a fresh window is opened and e.g. litegitpuller pulls in a different repo). There is a niche where different sessions should get fresh storage contexts, but within the same session some level of persistence is provided.
Proposed Solution
In addition to the local storage backend, provide access to the session storage backend. This backend is identical in functionality but limited to a single tab. Refreshing the tab persists the data, creating a new tab provides a fresh storage context.
The text was updated successfully, but these errors were encountered:
@juntyr could drives help with this use case? For example the default drive persists data in memory, which is lost on page reload. But an additional drive would persist data on a storage backend? Similar to what jupyterlab-github would do, but with actual write access.
creating a new tab
What does creating a new tab mean in this context?
Whereas localStorage is only connected to the site origin, and so even different tabs share the same storage, sessionStorage is unique per browser tab (so if I open the same site twice I will get two separate stores, but if I reload one of them it keeps the data). Does that clarify it?
Problem
When hosting a JupyterLite page, there is a balance between avoiding user data loss (by having a persistent storage backend) and not having independent sessions interfere (a fresh window is opened and e.g. litegitpuller pulls in a different repo). There is a niche where different sessions should get fresh storage contexts, but within the same session some level of persistence is provided.
Proposed Solution
In addition to the local storage backend, provide access to the session storage backend. This backend is identical in functionality but limited to a single tab. Refreshing the tab persists the data, creating a new tab provides a fresh storage context.
The text was updated successfully, but these errors were encountered: