That may be your opinion, but coding in unsafe or dastardly options creates support problems.

It's _MUCH_ easier to support and debug, maintain and upgrade logged-in functions. You have more control over the input, and you have access to all the USER-> values to track results.

IMHO there is really no reason NOT to have a user log in. No major site allows much functionality without getting some sort of log on, mostly for those reasons.

I've always thought it was a bad idea to not force a user to log on to "do" anything. To simply read, or search, is ok. But any time you get input from the user, they should be logged in. The reasons are increasing daily.

There are also some functions that simply make no sense without a logged in user, and cookies are wholely un reliable for anything other than place marking or logons (easily retrievable data). Storing anything, like the MyFav list, is more and more risky, and anti virus and spyware programs clean cookies out.

As the song says, "you do your thing, I'll do mine."


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.