a few of us are arguing this issue with no resolve, so i'd like everyone on this list to either post or respond to me personally and give your input. the result... i need as many responses for help make a case for either side. this piece in particular failed load testing so we're trying to decide why. if you have a really detailed response, post it to cf-talk. otherwise, save the list and send it to me c/o [EMAIL PROTECTED] subject of argument: a page that includes LOADS AND LOADS of nested CFMODULES. the page structure includes many, many more layers than the below, but you'll get the picture quickly: thisPage.cfm -- CFMODULE (1 attributes) -- CFMODULE (1 attributes) -- CFMODULE (4 attributes) -- -- -- CFQUERY -- -- -- CFQUERY -- CFMODULE (4 attributes) -- -- -- CFQUERY -- -- -- CFQUERY -- CFMODULE (4 attributes) -- -- -- CFQUERY -- -- -- CFQUERY -- CFMODULE (4 attributes) -- -- -- CFQUERY -- -- -- CFQUERY %% CFTRANSACTION %%%%%%%%%%%%%%%%%%%%%%%%%% -- -- CFMODULE (5 attributes) -- -- -- CFQUERY -- -- -- CFMODULE (3 attributes) -- -- -- CFQUERY -- -- -- CFMODULE (8 attributes) -- -- -- -- CFMODULE (2 attributes) -- -- -- -- -- CFMODULE (2 attributes) -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- CFMODULE (4 attributes) -- -- -- -- -- CFMODULE (2 attributes) -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- CFQUERY -- -- -- -- CFQUERY -- -- -- -- CFQUERY -- -- -- ** CFMODULE (2 attributes) -- -- -- -- -- CFQUERY -- -- -- -- -- CFQUERY -- -- -- -- -- CFQUERY (5-table join) -- -- -- -- -- CFQUERY (5-table join) -- -- -- -- -- CFQUERY -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- CFQUERY -- -- -- -- -- CFQUERY -- -- -- -- ** CFMODULE (5 attributes) -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFQUERY -- -- -- -- -- -- CFMODULE (10 attributes) -- -- -- -- -- -- CFMODULE (10 attributes) -- -- -- -- -- -- CFMODULE (10 attributes) -- -- -- -- -- -- CFMODULE (8 attributes) -- -- -- -- -- -- CFMODULE (3 attributes) -- -- -- -- -- -- -- CFQUERY -- snip -- %% CFTRANSACTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% that's about half of the page in question. now.... A says: CFMODULE was created to allow pseudo-function processing, allowing attributes to be passed in and out. Nesting them is proper OO programming/structure, allowing multiple reusable components, and CF should be able to handle this level of complexity. B says: CF was not meant to program as OO and this kind of CF programming is not scalable -- period. CF _CAN_ handle structure like this, but it is not proper CF programming for an application under load. Performance should not be sacrificed for proper OO structure or reusability. Any more than two levels of a CFMODULE, ESPECIALLY within a cftransaction, is not acceptable. again, if i get 300 replies to my personal inbox, i would couldn't be happier (i.e. power in numbers). just please don't clog cf-talk unless you have a really detailed response. -mike ([EMAIL PROTECTED]) ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/[email protected]/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
