i think for the ease of use, 1 db call per page is minimal, especially sinse we are talking about some small fields here. THe db is local to the webserver, so really, whats the problem. Jason
"Ed Lazor" <[EMAIL PROTECTED]> wrote: > > > -----Original Message----- > > I don't know - is it? > > I would think so. It's optimized for speed on small data sets. Does anyone > else have an opinion on this? > > -Ed > > > > > > > > > > > > > "Ed Lazor" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > > > > -----Original Message----- > > > > > The real reason for having the login class like this is to eliminate > > > > > database calls. I thought I could have one session variable that > > said > > yo > > > > > uwere logged in, but then the database calls would still have to be > > made > > > > on > > > > > each page. > > > > > > Playing Devil's Advocate here... > > > > > > Why would you want to avoid database calls? If you're using default > > > sessions management, all you're doing is trading this for accessing > > files > > on > > > the server. Isn't the database faster? > > > > > > -Ed > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
