I'm writing up some CFCs that control different parts of an application. ALL operations of a single type is in the CFC, so when someone logs in, all of the login operations (case sensitive password, session info, cflogin, etc) is in the CFC. It leaves less in the .cfm templates and makes it easier for a designer to work with the code. All they have to do is access the CFC for any 'real' operation and then make use of the returned data and maybe run a few CFIFs or the like. Makes for some really sparse and tight code.
But that's just me. :)
>
>Why are you using cflogin inside the cfc itself? Normally I'd use it in the
>application. Of course, this does not stop you from using Roles values in
>CFCs.
>
>
[
Todays Threads]
[
This Message]
[
Subscription]
[
Fast Unsubscribe]
[
User Settings]
![]()
