asp.net - Using sessions in user controls -


i use lot of ascx user controls in projects. these controls utilize update panels update contents. persist data across partial post backs (ie, when update panel updates) store controls data in session. example, might have control uses checkboxlist. when user checks box list, causes partial postback (to logic) , update panel fires. because panel updating, lose data between post backs, except store data in session. way, when control reloads, can take data , restore checkbox list. sessions typically consists of lists of objects.

my question is: best way persist data? possible problems might not accounting for? told if multiple people using @ same time (as lists of objects large) iis may run out of memory , crash.

thanks help

it's hard if "the best way persist data" particular project. can address "possible problems" part of question.

session state stored in-memory default, means using additional resources on server. session variables can created on fly , not require dispose of them explicitly can lead more overhead. yes correct using sessions of functionality mean using more resources (cpu , memory). whether "run out of memory , crash" matter of load vs. server.


Comments

Popular posts from this blog

node.js - Bad Request - node js ajax post -

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -