Is if faster to put global UDF's in a CFC... or to turn them into request/session/application scopes?
The question here is multi-fold, if someone had done the numbers. 1. Speed to instantiate and run the CFC, compared to a UDF. 2. Watch the scope so if there are changes the propigate correctly. 3. Code reuse... and "style"... i.e. - will you create a more global class? And have the "global" udf's inherit the class? Instantiating multiple classes can be more overhead... how does that compare with including more files for "global" udf functions. Note: None of the other functions are "structured"... so if we are thinking "functions" on a universal level... they may best serve us by working like the included functions. I have found no real issue with using an include and then turning the functions into global functions. John Farrar ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
