1)ASP 's Session State was stored in the same process that hosts ASP.
2)for different web servers, each Web server had its own session state.
There was a problem in sharing session states in a web farm situation.
3)No support for Cookieless sessions.
4)No web.config files for configuring the session state.
1)ASP.NET 's Session State is stored in the same process that hosts ASP.net(default)
It can also be stored out of process in an sql server database or a state server
2)different web servers can easily share the session state using the appropriate
3)Supports Cookieless sessions.(<sessionState cookieless=true/>) in web.config file.
SessionId is visible in the browser.
4)uses web.config files for configuring the seesion state.
Asked In: Many Interviews |