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
I have a singleton service that I register at startup in both the Server and Client projects. As the user navigates through the site on the Server, they eventually migrate to the WebAssembly site, but when this happens, they start all over again with a new instance of that singleton service absent everything changed on it over the course of their journey server-side.
Surely this isn't some esoteric requirement - have I missed something that illustrates how to keep users from effectively losing all context mid-browse when they transition to the WASM app or is this something that simply needs to be anticipated somehow? How is anyone else handling this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a singleton service that I register at startup in both the Server and Client projects. As the user navigates through the site on the Server, they eventually migrate to the WebAssembly site, but when this happens, they start all over again with a new instance of that singleton service absent everything changed on it over the course of their journey server-side.
Surely this isn't some esoteric requirement - have I missed something that illustrates how to keep users from effectively losing all context mid-browse when they transition to the WASM app or is this something that simply needs to be anticipated somehow? How is anyone else handling this?
Beta Was this translation helpful? Give feedback.
All reactions