you should absolutely minimize the amount of things you keep in the session, IMHO. The database is made for scaling like this, session objects are not.
Basically the database will be able to handle concurrent uses better than cramming data into the session. I store very little information in the session, especially because the more data you store there, the less scalable your application becomes. just my 2 cents --- minimize. fillup On 5/23/02 10:10 AM, "Richard Diaz" <[EMAIL PROTECTED]> wrote: > I'm currently doing DB Queries and holding the users > information in session objects... trying to keep the > query load on the database down to a minimum by using > these session objects (MVC2). > > My question is where do I draw the line as far as how > much RAM each user gets? When do I free up those > session objects and querying the database for > information again? > > Are there any guides on this? > > thanks in advance, > Rich > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
