Optimization

7 Apr 2005 3:15 PM

SirPyros

I'm building a shopping cart solution. In terms of scalability and
perfomance for the server, which is better, only storing a small
variable in session state to denote a cart and load information from
the database and calculate values for the cart every time they need to
be shown, or save item id and quantity information in a class and store
it in the session, then as values are calculated they are stored in the
class to be used later if no items have changed.

7 Apr 2005 3:37 PM

Joseph MCAD

April 6, 2005

If you haven't specifically secured your session state, then it is a rule
of thumb not to store anything in session state that you base security
decisions on later. This would force your decision to use the database. Hope
this helps! :-)
Joseph MCAD

Show quoteHide quote

"SirPyros" <SirPy***@hotmail.com> wrote in message
news:1112886957.622593.312110@z14g2000cwz.googlegroups.com...
> I'm building a shopping cart solution. In terms of scalability and
> perfomance for the server, which is better, only storing a small
> variable in session state to denote a cart and load information from
> the database and calculate values for the cart every time they need to
> be shown, or save item id and quantity information in a class and store
> it in the session, then as values are calculated they are stored in the
> class to be used later if no items have changed.
>