> creating and writing the dynamic CFC should be a one-shot deal I really hope so.. This is what I'm not sure of. Because it seems like in order to generate a dynamically generated function, it requires using CFFILE to write the .cfm/.cfc, and if this is required every time, it is going to be very costly in performance...
Henry >I also believe the actual proxy CFC code should only be generated once. >However, since I haven't used AOP with a non-Singleton ColdSpring-managed >object, I am not 100% sure. Are you sure what you want to do can't be >handled with a Singleton using AOP (that internally may interact with a >per-request CFC), rather than a per-request CFC for everything? > >The only "performance issue" with using ColdSpring for per-request CFCs is >the overhead that ColdSpring goes through checking for any dependencies that >need to be wired up. ColdSpring internally caches all of the bean >definitions and their dependencies internally, so the overhead is fairly >minimal. However, if performance is an issue and you are trying to generate >large numbers of per-request CFCs, you're probably better off writing your >own factory to create them (and have ColdSpring inject the factory into the >service objects that need to use it). > > > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get the answers you are looking for on the ColdFusion Labs Forum direct from active programmers and developers. http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid-72&catid=648 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:290363 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
