At 4:01 PM +0000 3/13/08, Stut wrote:
tedd wrote:
Then, when the user returns, you simply check the cookie with
what's stored in the dB and continue as before. If the check fails
(no session id or it has been altered), then start again.
Because that negates the whole point of doing it which is to reduce
database access to the minimum possible.
Oops, I guess I missed the whole point of your article.
You want to minimize dB usage by using an encrypted cookie so that
when users return, that action doesn't use the dB.
But, once the user is on, then everything they request in the form of
unique data is provided by the dB via their user id, correct? So, you
saved one trip to the store, but how many trips to the store does a
user usually make? And is that worth it?
Not being critical, just wondering.
Cheers,
tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
