Actually, I disagree with Scott, somewhat...
While the amount of data in the variables does increase the size of the data
stored, it's the number of variables that greatly increases the complexity
of your application. Programmers fight complexity. That's one of our jobs.
Now, the amount of data
Actually, I disagree with Scott, somewhat...
While the amount of data in the variables does increase the size of the data
stored, it's the number of variables that greatly increases the complexity
of your application. Programmers fight complexity. That's one of our jobs.
Now, the amount of data
Actually, I disagree with Scott, somewhat...
While the amount of data in the variables does increase the size of the data
stored, it's the number of variables that greatly increases the complexity
of your application. Programmers fight complexity. That's one of our jobs.
Now, the amount of data
I've inherited an application that uses session variables all over the
place.. I think every form variable has been moved to the session scope.
I'm in the process of documenting them, and I have 67 variables
documented so far.
My question is: How much is too much and will having this many session
Scott Stewart wrote:
My question is: How much is too much and will having this many session
vars affect performance.
It is more if the amount of data in the variables then the number of
variables. One session variable containing a 5k structure will have
more of a performance impact the
5 matches
Mail list logo
