Joe, As long as your CFC's are inherently "dumb" - that is they get/set based on the input provided by your controllers (or the template that calls the instance) you should be able to safely place them into the application scope and re-use them - avoiding the overhead of multiple instances.
If you do so, though, you will need to be aware that the 'variables' and 'this' scopes of that component will also be in the application scope. If you are changing variables in those scopes during the course of a request, you will want to move those to the arguments scope of your methods (or var scope them if they don't need to change and are only used by a method or two). Option B, for components that are not required on every request is make those 'singletons' and re-instantiate them every time they are used - more overhead on the request, but less for the application as a whole if they are used infrequently. I would suggest checking out Coldspring. It is exceptional for handling just this type of issue. HTH, Jon 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275038 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
