is there a difference if i use either cache or session to store values for current user.

Ahmed Ali
Software Developer

__________________
Ahmed Ali
Senior Software Developer

Try using the cache and see what happens. I think you'll find that if you store x=1 in the cache for one user, any other user will also see x=1. The cache, to my knowledge, is not user (i.e. session) specific.

Peter
------------------------------------------------------
Work smarter, not harder.

do you mean on one machine,if user1 logout, and user2 log in on the same machine the data will remain, till now i do reset the cache after i finished using it.

finally is the cache like Application stored glopally???

Ahmed Ali
Software Developer

In some respects, the Cache is similar to Application state in that it stores information accessible for all users. Application state is not available for other servers in a Web farm scenario, and AFAIK, the same is true for Caching.

Caching allows you you to cache frequently used data, like the results of a complex query that takes a long time to run. Storing it in the cache allows you to easily reuse it without performing the same query again. The advantage of the cache is that it can clear itself automatically (i.e. when your server runs out of memory) or that you can bind dependencies to caching (i.e. remove from the cache in 20 minutes, or remove it when file X changes). This is not possible with the Application sate, so if you store too much info, your server will run out of resources.

But how about you do a little Google-ing for this? All the information you need is available on the Web.

http://www.google.com/search?hl=en&i...he+application

http://www.google.com/search?hl=en&l...=ASP.NET+Cache

http://msdn.microsoft.com/library/de...asp?frame=true

ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/cpguide/html/cpconcacheapis.htm


It's all there. IMO, doing some investigation yourself is much more rewarding than posting a question here and waiting a day or so for an answer.....

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Then what's the point of using the cache??

Peter
------------------------------------------------------
Work smarter, not harder.

ok thx all,
i got it,
i have got these line from MSDN,
The main difference between the Cache and Application objects is that the Cache object provides cache-specific features, such as dependencies and expiration policies.

ASP.NET introduces a new key/value pair object—the Cache object. The scope of the ASP.NET cache is the application domain; therefore, you cannot access it from other application domains or processes. The ASP.NET Cache object's life span is tied to the application, and the Cache object is re-created every time the application restarts, similar to the ASP Application object.

finally
i have understood that cache is used for heavily used data per domain for example a query result is cached for each request for all users access the same domain within a defined timeout determined by the first calling user for these query, but but but i am not clear about that and still ambiguous



Ahmed Ali
Software Developer