Ron

• Jul 10th, 2007

 

1. In-Proc: the default provider.
2. Session Service: ASPNET_Session service. a diff service, runs outside IIS's service. pros: in case of app recycle - the session remains the same; helpful when it's a web garden. cons: cross process communication (performance)
3. Sql session provider: single point for sessions. remains on disk. pros: a web farm solution; survives power failure; cons: performance (disk i/o).
4. custom: build your own provider :-)

kirangiet

 Profile Answers by kirangiet 

• Sep 10th, 2009

 

Session Management can be achieved in two ways

1)InProc
2)OutProc

OutProc is again two types
1)State Server
2)SQL Server

InProc
Adv.:
1) Faster as session resides in the same process as the application
2) No need to serialize the data

DisAdv.:
1) Will degrade the performance of the application if large chunk of data is stored
2) On restart of IIS all the Session info will be lost

State Server
Adv.:
1) Faster then SQL Server session management
2) Safer then InProc. As IIS restart
won't effect the session data

DisAdv.:
1) Data need to be serialized
2) On restart of ASP.NET State Service session info will be lost
3)Slower as compared to InProc

SQL Server
Adv.:
1) Reliable and Durable
2) IIS and ASP.NET State Service
restart won't effect the session data
3) Good place for storing large chunk of data

DisAdv.:
1) Data need to be serialized
2) Slower as compare to InProc and State Server
3)Need to purchase Licensed
version of SQL Server