General question regarding if it is advisable to replace session state store with viewstate in an attempt to reduce memory pressure and general server performance:
Current architecture:
Asp.net 2.0 app using Datasets to transmit data from DataAccess layer to UI
Intranet app ( but exposed to maybe 20 internet users )
UI stores a decent amount of datasets in session currently ( in proc session that is )
Heavy use of AJAX.Net so lots of async postbacks
No web farm currently but plans to move probably
150 - 300 total users ( maybe 20 simultaneously but not sure )
My concern was that by putting our datasets in viewstate, we are going to force a lot of work on the server ( not to mention garbage in the runtime ) to serialize the dataset back and forth. And, we use a lot of ajax so viewstate is being pushed up and down much more often than the typical case. Now I know that by removing t ...
Go to the complete details ...