|
summaries and tech views for new developers C#,asp.net for web\mobile development,databases,iis6 and more.
Creating this site was an idea that popped up after some programing years,
when you have to get back to the same things you all ready forgot,
while new stuff is arriving to town.
In this site you can find summaries on tech stuff im into,
so for a stable wide base knowledge pyramid ,enjoy!!
|
|
Session State
Web applications often have a requirement for managing information that is carried over from one
HTTP request to another.
For example, this information could include a logged-on user’s name, their
role, their shopping cart contents, and so on.
HTTP protocol is stateless,
In a load-balanced environment, each HTTP request from a given client might be routed to a
different web server, so storing that state information on the web tier won’t work.
The usual approach is to set a session ID cookie. The session ID is a key
that’s used to store the client’s serialized session state.
An alternative approach is to use cookieless session IDs, where the session ID is placed in the URL.
which is a potential security risk.
InProc OutProc
In the outproc mode the session will be maintained in the SQL Server.
If we use the inproc mode, the session will be maintained in the IIS itself.
We go for outproc mode if we have developed a webfarm i.e. one application deployed in more than one server.
the problem is when your DB is connected to many web servers .
|
