ASP.NET Masters: What are the advantages / disadvantages of using Session variables? -
I have already done a search on this topic, and I found more of that data - one review is three different - Different types of sessions (InProc, Sql, StateServer) However, my question is of a different nature.
Specifically, what are the advantages / disadvantages of using the NAT session created in the first place?
That's why I'm asking: A partner .NET developer has never created me in the Microsoft session. Not at all. A custom session did not even create a state provider. The reason for this is the following - if you have a session running then it decreases all your requests synchronously. They say that the competent session reduces the performance of a web server.
The solution is to create yourself a session - a class that stores all your essential values and is sorted in and out of the database. He recommends that you store unique IDs to refer to it in a cookie or query string variable. In our environment, using DB to store sessions is a requirement because we are all in web fields, and we use Oracle - so I agree with that part.
More than a home-created session performed below the session?
So what are the advantages / disadvantages to do all this?
Thanks for all the answers! First, a browser makes only two requests for a given hostname given at a given time.
ASP.Net Session Status (SQL Mode, State Server, or Custom) You have a standard implementation, and is consistent across an application. If you do not have to share session information then this is your best bet if you need to share information with other application environments (php, swing / java, classic ASP etc.), it's worth considering It is possible.
Another advantage / disadvantage is that the developer focus
Comments
Post a Comment