Does System.Web.Caching.Cache make sense in an ASP.Net MVC app?

Question

Since there is no concept of sessions in ASP.Net MVC and each request is independent of each other would I ever make use of the Cache object to internally cache data in order to minimize db access? The output caching functionality is great for caching view data but if I wanted to cache something like a user profile which should be shared amongst requests from the same user what would I do?

Thanks

Answer 1

Use Session?

Session is per user's session Cache is sitewide for everyone

You could use caching on the controller I suppose.

Answer 2

There is certainly the concept of a session in MVC... Session data is persisted across requests. I think you may be confusing that with ViewState, which is persisted across postbacks to the same page and isn't applicable in MVC.