What is best way to maintain the reusable data in mvc4 until the application close.

Question

1.00/5 (1 vote)

See more:

If I want to maintain filtered data into entire application functionality which technique is suitable to main that.
The data should be available in entire my functionality and should not destroy whenever the navigation happened from one action to another action.

Posted 8-Sep-15 4:19am

DGKumar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2015-09-08T04:32:00

Solution 1

Use the Session

https://msdn.microsoft.com/en-us/library/ms178581.aspx[^]

I'd only recommend this if the data to be kept is small, or the number of concurrent users is small.

Posted 8-Sep-15 4:32am

F-ES Sitecore

Comments

DGKumar 8-Sep-15 10:50am

If i use session that will not differentiate into multiple tabs. I want to maintain session id with guid. Is this suitable approach to generate unique session id to maintain different data for different tabs?

F-ES Sitecore 8-Sep-15 11:00am

If session survives tabs depends on how the browser implements tabs. If you want to guarantee tab-safe usage you'll need to effectively manage your own sessions. Create an ID you store to a persisted cookie (give it an expiration date) and store data in the Cache with that ID as a key. To get that user's data you get it from the cache based on the key read from the cookie. Your challenge is then deciding when to clean that data up. Easiest would be to give it a sliding expiration time, but in that case you'd need to keep updating the expiry date of the cookie too to try and prevent a situation where a user has a valid cookie but no matching data in the cache.