I have an ASP.NET Core application with Blazor pages featuring a sidebar containing five URLs. Each page consists of 15 input boxes. I need the input data to persist after page refreshes or when switching between URLs. Additionally, this data should be accessible in the backend for calculations. Considering the presence of a login page, the input values and backend data should be specific to the logged-in user. I've considered using server-side session storage, but I'm unsure if this is the most elegant solution. What are your suggestions for achieving this functionality?
Specifically, I'm looking for recommendations on how to:
- Preserve input data across page refreshes and URL switches.
- Store the input data securely and efficiently on the server, ensuring it's only accessible to the logged-in user.
- Maintain a connection between the input data in the frontend and its corresponding representation in the backend for calculations.
- Explore alternatives to server-side session storage if it's not the optimal solution for this scenario.
Any insights, recommendations, or best practices would be greatly appreciated. Thank you.
I must admit that I haven't delved into implementing any specific solutions yet. While I'm aware of the concept of server-side session storage and browser local storage, I haven't attempted to integrate them into my ASP.NET Core Blazor application. My hesitation stems from uncertainty about the most appropriate approach and concerns regarding scalability, efficiency, and data security.