[EMAIL PROTECTED] wrote:
To today I did this with storing a value in my per-user-session, that
marked a logged-in user with 1 and a non-logged in with 0.
In every following component I checked that value (with direct code,
functions, modules ... whatever, not the question here).
Is there a better way? To fill in every afterwards-component checking
code is imho a bit clumsy.
Its not a problem in sites with less security so user navigation is
done by the clickable links. But whats the matter if the user - out of
possible links - inputs an non-allowed url so he is out of the
programmed path.
One way to make sure everything is protected, is put what needs
protected into it's own directory.
You can then add an autohandler to that directory, which redirects the
user elsewhere if they
are not authenticated.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
