|
Doesn't the CFLOGIN tag just set an encoded cookie?
In that if you attach other variables to the CFLOGIN scope, it may not encode
them as it only expects a pre-defined value set.
Well, I personally have a "person" object
instatiated into the session scoep, when a user hits my applications. When the
initialization of the person object begins, it fires a method to check for
isLoggedIn(), which depending on your security model does a check for the
correct security creditentials (ie cookies etc).
If it comes back as rejected, the
person.isLoggedIn() is "false" which you then do your login procedure etc
etc..
When I use CFLOGIN, I generally also keep the roles
a user belongs to in an array, as a property of the User. Its mainly for things
that CFLOGIN can't have control over and for times when you need to get what
roles a user belongs to (you could just db lookup that user, but while your in
the DB in the first place and doing a handshake, it can't hurt to store the
details in the person object).
I've found using a Person object opens up lots of
doors, for scaleability accross multiple applications in that you could say have
two shopping carts per person for two sites and all refer to the one user? and
then when you need to log any movements its as simple as
person.logThisPage(true); when you want to dump the users movements through an
application.
Scott.
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/ |
- [cfaussie] RE: cflogin Scott Barnes
- [cfaussie] RE: cflogin Steve Onnis
- [cfaussie] RE: cflogin Knott, Brian
- [cfaussie] RE: cflogin Mark M
- [cfaussie] RE: cflogin Steve Onnis
- [cfaussie] RE: cflogin spike
- [cfaussie] RE: cflogin Phil Evans
- [cfaussie] RE: cflogin spike
- [cfaussie] RE: cflogin Phil Evans
- [cfaussie] RE: cflogin spike
- [cfaussie] RE: cflogin Phil Evans
