>Just a quick thought: If, for example, you are building reusable, >singleton components (sorry for the OO buzzwords, but it is descriptive >terminology), then you can load those CFCs into Application scope and have >them exist in memory only once but still be used across all requests in the >app.
Putting a CFC in the Application scope is *NOT* creating a Singleton. A CFC in the Application scope is an instance of that object, but there is nothing stopping you creating multiple instances of that CFC - whether still in the Application scope or other scopes. A Singleton is an object that *can only have one instance*, returning that same instance even if you try to create a new instance. And, particularly with OO, the times when you actually want an enforced single instance are rare - so if someone starts talking about Singletons, there's a good chance they've misunderstand OO's concepts. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326096 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
