The rumor is that the page context bug won't be fixed anytime soon.
Rumor? I've posted here and elsewhere that this is a complex bug to fix which is why it hasn't yet been fixed - it will take quite a bit of engineering to fix this properly.
Of course, there are also some people who think that the page context bug is a cunning ploy to discourage certain "bad practices"... [that's a joke, by the way, for the humor-challenged]
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.
Certainly no problem with stateful CFCs. I think the problems to which you refer can mostly be traced to attempts to do one of two things (or possibly both at the same time):
1. trying to use cfproperty and "reflection" to describe persistent properties and then walking the CFC metadata to generate SQL.
2. trying to create generic base classes (mostly that do (1)) so that every instance created carries lots of "baggage" in terms of inherited methods and so on.
There are ways to mitigate the overhead involved in both of these but, as usual, algorithmic / design changes can bring greater performance benefits...
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).
