- when first client makes a request to the server ,asp.net worker processer will create a block of memort for individual users.
- sessions will expire after a certain amount of minutes, as configured in the web.config file.
1)InProc
2)OutProc
OutProc is again two types
1)State Server
2)SQL Server
InProcAdv.:
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
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
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
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 serializedwhere they are stored.
2) Slower as compare to InProc and State Server
3)Need to purchase Licensed
version of SQL Server
2) Slower as compare to InProc and State Server
3)Need to purchase Licensed
version of SQL Server
1. inproc - default stored in web.config.
2. outproc - stored in server side.
3.Sql server - stored in database.
2. outproc - stored in server side.
3.Sql server - stored in database.
No comments:
Post a Comment