Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I currently using my own membership implementation on a ASP.MVC project. I’ve got an Account and an Account can have more than 1 memberships.
I am not sure what is the best approach to follow with Account information being cached. I am currently loading the account information for almost each request from the User property of the controller.
Should I cache the account information? And if where would be the best place, cookies or Session?
I recommend fairly strongly against sessions. They won’t scale well and do not fit into web/HTTP type of architectures. See ‘Key REST principles’ in this REST article if you like the REST stuff.
I would suggest to put the user information in cookies (don’t over do it, just really required stuff).
And keep sensitive information in the ASP.NET Forms authentication cookie. See Forms Authentication article, “Step 4: Storing Additional User Data in the Ticket”.
Fetch the rest of the data from the database. Avoid premature optimization.