> typically use <cflogin> within my application.cfm files. My CFCs will
handle
> stuff like, authentication, getUserRoles, etc, but the actual mechanics of
>
> prompt for login
> use cflogin if authenticated
>
> are handled by the Application.cfm file.
Do you mind if we discuss this for a little while? I have a lot of
conceptual questions that maybe you could answer. I'll even paste my current
application.cfm file that I've been using for a while, which I seem to
recall you kinda helped me with last year.
For instance:
I'm not *sure* why I want to do cflogin inside the CFC. For one, I was
wanting to create something that, with minimal effort, could be used with
Flash Remoting. I'm creating an application that's going to require some
basic security (IE, you gotta be logged in to use it) and eventually I was
wanting to springboard into creating it as a Flash Remoting Application down
the road. In fact, I was hoping to learn Flash Remoting using this as a
starting point, but first wanted to get it up and running as a CF solution.
Right now, I'm concentrating on the logging in...and I'm not worried about
the actual functionality of the application. That can come later. I just
want to make sure I can "CFC-ify" what I've currently been using in a "best
practices" manner.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
