@Matt Quackenbush
thanks so much for taking the time to help me out :) that makes sense. kinda
starting to get it. I think its going to be one of those things I need to do
real world things with before I see the benefits. at the moment all I seem to
be doing is adding extra overhead lol.
is
how do you organise your apps?
That is where using ColdSpring for your service factory would come into
use.
It handles the relationships between your singleton components.
You can use create your all your gateways etc.. and it will wire them all
together for you.
On Sat, Aug 15, 2009 at
The more I venture into OO type of design the more I have to get my head around
todays its getters and setters. I think I am 'getting' in to the swing of
this but I could do with some advice please! any advice and help is welcome!
I have no idea if I am just making this up as I go along
I'm not sure exactly what the question is, but in a brief glance of the code
it appears that you have the general concepts correct. My concern is this
bit:
admin.cfc --- getters and setters, right?
I don't know what admin.cfc is, but based upon the context I am assuming it
is intended to be an
I respectfully 100% disagree. You should **ALWAYS** validate ___ALL___ data
that comes from your users.
(Note the period at the end of that sentence.)
On Fri, Aug 14, 2009 at 3:57 PM, Kevan Stannard wrote:
If you are just logging in a user then you probably don't need the
validation
Can you provide a few more details on what you are trying to do? If you are
just logging in a user then you probably don't need the validation steps.
// Returns zero if not authenticated, else returns a User object
var user =
Ah, good point. What I meant was that for a typical user/pass authentication
scenario then no explicit validate() function would be required. The data
must be sanitized but I expect this would be this would be implicit in the
authentication code rather than an explicit step that returned a
7 matches
Mail list logo
