I have custom UserInfo and UserAuthorization objects in my app, which determine what is displayed and what actions a user can perform on each page. At the moment this information needs to be retreived for every request to the server. Would it be possible/sensible to cache this information somehow? Can anyone suggest some good google search terms as I haven't managed to find anything. Thanks.
+1
A:
Would it be sensible to cache this information somehow?
No. You could probably use session state if you really wanted but have you determined that loading this user information per request is really an issue?
Graphain
2010-07-30 08:59:42
No I haven't noticed performance issues as yet, but I'm only running on my local machine at the moment. I'd like to reduce the number of remote server calls partly because it just feels messy to have to pull data from so many places all the time. I thought user caching was fairly common. If you think it's a bad idea though, that's a good enough answer for me.
fearofawhackplanet
2010-07-30 10:01:55
Why would you be pulling so much data? It sounds like on each web request you're accessing 4 or 5 databases to validate the user. Why?
Graphain
2010-08-02 00:32:00