When I said a hundred methods - I meant over all cfc's in an app. Not in a
single cfc - that would be crazy. But I still have trouble remembering
method names when "gluing" them together to form the main processing of the
app.
Hmm, then it sounds like your names are not intuitive enough (or descriptive enough). If your CFCs and methods are well-named then code should read like 'natural English' and it should be fairly easy to remember the method names...
We're currently in the process of redesigning our main product and
are considering such an architecture. However, while disassociating the
display from the business logic is easy, disentangling the database access
from the business logic is much harder. It's such a radical change that we
may rewrite with that in mind and then factor the database access out
afterwards.
You'd probably do better to spend a bit more time designing the separation of the business logic from the data model so that you end up with a cleaner solution. Mind you, good design is hard. Good luck!
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
