Will the static get accessor of a property be cached ?
-
Hello, I have 2 closely related questions, would you please help. 1. In my ASP.NET MVC application, I am encapsulating the Logged In User Name within a static property in a class as
public static string LoggedInUserName
{
get
{
return HttpContext.Current.User.Identity.Name;
}
}Now, I am wondering, as the property is static, will that value be cached so that if a new user visit the website, the last returned user's user name will be returned by the Property ? I am expecting that, every call to the property 'LoggedInUserName' the fresh new Identity value will be returned. Am not I right ? 2. If I want to cache a value within the application life cycle, I know I can use a static field. But, is it required that the static field be public ? Or any private static field is also cached within the application life cycle as well ? Regards.
-
Hello, I have 2 closely related questions, would you please help. 1. In my ASP.NET MVC application, I am encapsulating the Logged In User Name within a static property in a class as
public static string LoggedInUserName
{
get
{
return HttpContext.Current.User.Identity.Name;
}
}Now, I am wondering, as the property is static, will that value be cached so that if a new user visit the website, the last returned user's user name will be returned by the Property ? I am expecting that, every call to the property 'LoggedInUserName' the fresh new Identity value will be returned. Am not I right ? 2. If I want to cache a value within the application life cycle, I know I can use a static field. But, is it required that the static field be public ? Or any private static field is also cached within the application life cycle as well ? Regards.
To the best of my knowledge, none of the code you write or compiled is cached. You seem to have the term cache confused with the session state of the http server (web server)and the relationship of the http context that is created for each browser that connects to the http server.
-
To the best of my knowledge, none of the code you write or compiled is cached. You seem to have the term cache confused with the session state of the http server (web server)and the relationship of the http context that is created for each browser that connects to the http server.
Hi, Thank you so much for your reply, actually I meant cache not by the Http Cache. I meant, I can keep the data live in the Memory as long as the Application is live (Web.Config is not modified or application is not restarted). So, do you think, my Public static get accessor will return the same data for every time just because it is static ? I know if I used a static field inside the get accessor than, the value is not lost from memory.
-
Hi, Thank you so much for your reply, actually I meant cache not by the Http Cache. I meant, I can keep the data live in the Memory as long as the Application is live (Web.Config is not modified or application is not restarted). So, do you think, my Public static get accessor will return the same data for every time just because it is static ? I know if I used a static field inside the get accessor than, the value is not lost from memory.
No, The data lives in the web servers session context, your just writing code that talks to the web server if the data exist. So you also need to make sure that the data exist before you ask for the data, or else the code will bomb with an object not found. Once the session expires, usually 20 minutes, that's it, the handle to the web servers session context is deleted, and your data is cleared. You can't store session data forever, it's has a short ( finite ) lifespan. If you want to store temporary data, then you write to the database on the server side, or write a cookie on the client side. And ask the browser for the cookie if it exist thus - Request.Cookie 3rd edit: Don't worry about the code, or whether it is public or private. Technically, the object should already be global, in which you can access the data on another web page using the same code. If your using the code to remember who the user is, on many pages after they sign in, then your alright. Just make sure to check the identity when needed.