May 29, 2019 05:04 PM|bitbrain|LINK
I can't give you a way to prevent it, I can tell you how I handled it though.
I set up a service, which is really just a class with an interface. I store my data in the service. If I need to store it between sessions, I can store it in a database.
With client-side Blazor, you can use a singleton service I believe. And it will be matched only for that session with that user.
On server-side Blazor, I have to have a unique id because I don't think scoped worked how I thought it would work. So the data just gets stored alongside other sessions in a List<session> sort of thing. I don't need it crazy scalable because the max amount
of sessions going on at any one time will 10 or 20 because this is an internal app.