Hi,

Does your application need the user data to be cached even after the session is closed? If this is not a case, store data in Session rather than in Cache.
You said that you will be appending the sessionid to the cache item name, which means that the data is not useful once the session is closed. So, storing data in cache unnecessary, as it is application scope increases load at the server. So, rethink about storing data in Cache object. Better store data in Session Object.

You can access data from the database instead of storing it in Session also. But, the tradeoff is between at how many places does you need this data. If it is required at fewer places (<15) for a huge application, then better go for DB every time. But, you need to consider the amount of other data storing in session. Also, consider the number of users accessing your site simulatenously. Because, if you are storing data in session and number of people accessing the site is hight, then you can get memory problems.

__________________
Venkat
knowledge is Power

Hi Venkat,

thanks for your reply, i need little clarification on it. I will use the session.
My doubt is where these values will be stored in server and is any difference between these in performance....


thangs again venkat....


thnx....

Hi venkat,

i got the difference between cache and session and here it is.


Cache: The concept of Caching used in case of Performance Improvement.When web pages do not frequently change we use the concept of caching.All the object stores in the

memory .There are two types of caching 1) output caching 2)Fragment Caching .

it basically reduce the load of web site.

Session: Session object is basically used for Specific User and maintains its state.The

default Timeout is 20 minute but you can reset the time ,you can store any

object in session and also remove it.

Ex: Session["mysession"] = "This is my Session"


thnx...