maintain and reuse than large generalized ones. In OO terms, this is
called "cohesion", and it's a Good Thing. It means an object has a
specific and well-defined purpose and isn't trying to do a lot of
unrelated things.
HTH,
Brian
----- Original Message -----
From: Michael Kear <[EMAIL PROTECTED]>
Date: Wed, 14 Jul 2004 17:36:59 +1000
Subject: CFCs - more smaller or fewer bigger ones?
To: CF-Talk <[EMAIL PROTECTED]>
I am laying out the CFCs I need for a new site, and wondered if there was a
'best practice' for the way to assign the methods to CFCs.
For example when I think about users for the site, there are a number of
methods I need related to logging in and logging out, maintaining user
details, sending e-newsletters, listing users. Is there any advantage or
disadvantage to having all those functions in one 'Users" cfc or is it
better to have smaller, more specialised CFCs. Perhaps in this example a
UserMaintenance CFC and another UserLogin CFC?
I understand about the re-use opportunities, so I think methods related to
this site alone should be on their own, but in general terms, is it better
to have fewer, larger CFCs or more but smaller and more specialised ones?
Cheers
Mike Kear
AFP Webworks
Windsor, NSW, Australia
http://afpwebworks.com________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
