Implement/Add useCrossTabSessionStorage hook - #2575
Draft
JohnC-80 wants to merge 3 commits into
Draft
Conversation
… for non-React code.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on comments for https://folio-org.atlassian.net/browse/STCOM-1460?focusedCommentId=276289
done to enable implementation of https://folio-org.atlassian.net/browse/UISAUTHCOM-98
We've ideanated about something that carries the ephemerality of session storage, but exists cross-tab like localstorage... this is a bit of both.
Localstorage uses a tab registry (unique id's + timestamp) per tab. Values are stored in sessionStorage on a key designated by the app.
A new tab registration (writing to localstorage) will be picked up in a session event. The catching tab will broadcast its value to sync the new tab.
Current 'live' registrations prune on a 5-second heartbeat with a stale threshold of 15-seconds. Each tab is responsible for keeping itself alive and updating this timestamp. If it's old, it gets cleaned.
Pushing this PR up in draft for discussion.