As I am sure that my question will reveal, I am pretty new to CFCs.
I have toyed with CFCs, but this is my first attempt to use them in production. The site needs some separation between logic and presentation and may eventually need to serve web services.
I have a Security.cfc (that is actually called from a root-level System.cfc). I also have a Session-scoped User.cfc.
I am trying to figure out the "correct" way to handle a login. My first thought was to have my login handled by my Security.cfc which would in turn call Session.User.Login() if successful.
That feels wrong, but I can't quite figure out what would be right.
Should I have a User.CheckLogin() action that would call out to the Security.cfc? If so, do I call out to Application.System.Security.CheckLogin()? That still seems wrong (although I am not sure why). The only other approach that comes to mind is to invoke the CFC directly, but that seems pretty wasteful since it is already in memory.
What am I missing? Is my whole approach in need of re-evaluation or am I just missing a small piece?
Any help would be greatly appreciated.
Thanks!
Steve
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
