> As regards use of CFCs for MVC implementations, I'd have to say, in my > experience, that the primary difficulty would be the Page Context bug. > Personally, I have not found it too difficult to deal with this. > Ultimately that problem will be solved. IMO, there is too much value in > what CFCs have to offer to not use them. I need some compelling > information to dissuade me from this course of action. > The rumor is that the page context bug won't be fixed anytime soon.
> It is of concern, however, because you don't want to make architecture > decisions on large projects that work out to be bad ideas. I'm there > right now, architecting a large web site for a university. So when Matt > says that CFCs won't scale for the Model, then I need to know what the > story is. There is the question of what he refers to as the "Model". Are > we talking using persistent CFCs for modeling? What situations or usages > caused problems? Are there some code samples we can see? > The main issues with CFCs being used as models in MVC seem to be related to persistence and complex inheritance hierarchies. The basic rule may turn out to be that CFCs in general shouldn't be stateful. -Matt ---------------------------------------------------------- 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).
