that's what I thought. I figured db calls is more resource demanding than
these few session variables. I like doing these web applications, they're
more controllable. Public websites have more considerations. Thanx.
"Steve C. Orr [MVP, MCSD]" wrote:
[color=blue]
> If you've only got only 25 users and only 8 session variables for each, you
> should have nothing to worry about.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
>
http://Steve.Orr.net
>
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:9B8AD4B9-68AB-4795-8B93-FB76EAE28C00@microsoft.com...[color=green]
> > If given, maybe 25 users on my ASP.NET web app what is setting too many
> > session variables?
> > What are the draw backs of setting 8 session variables?
> > I thought about on each page making another db call to get user info and
> > just set 3 session variables, but isn't that more resource consuming?
> > what is ideal?
> > This is the age old "setting login information".
> > Is there a better way to manage this?
> > thanx.[/color]
>
>
>[/color]
