Hey Joe,
I'm not entirely up to speed on the internal mechanics of CFCs, but I
seriously doubt a reference for each method of each CFC instance is
created. Because they're basically a procedure, the method classes
as only needed in a static manner - no actual instances should have
to be created.
Doing things like get("foo") and set("foo") is poor OO design, and
falls into that "overoptimization = root of all evil" category.
-Joe
On Apr 11, 2007, at 2:06 PM, Joseph Frank wrote:
> Apparently, each method in a CFC turns into its own compiled Java
> class in addition to the CFC itself. If I generate setter/getter
> methods for each of my class properties, wouldn't that be an issue
> in terms of scalability?
> For example, instantiating this CFC into Session scope, instead of
> what seems to be a single class per application user, now I have 30
> class references per user.
>
> Any thoughts?
>
> Joe
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 by Adobe®
Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7.
Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275042
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
