One other thing I'm doing is putting each section of code into its own subdirectory and each operation has its own page. No index.cfm?fuseaction=whatever or the like. A page does something and is called based on what it does. No running around to put a page into an interface in one place and a bunch of strangly named files in another. segmented pages, plain names and tight code in objects. Simple, to the point and no bulkly 'extras'.
>You can certainly have the CFC handle authentication, grabibng roles, etc,
>but you can do so w/o using <cflogin> or <cfloginuser> in the CFC itself. I
>don't know why - but that just seems wrong to me. I guess because I think
>the CFC shouldn't be tied to the login method itself - ie, it should simply
>say that u=X,p=Y is a valid username/password, and let the caller handle
>storing (in session, cflogin, whatever) that the user is now authenticated.
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
