> Sean wrote: > Since you should only be loading the functions you need in each page, it isn't going to be inefficient.
And I think this brings up an additional interesting point related to the original question: How should you manage only calling the necessary function libraries on each request, instead of including/referencing all of your UDF libraries on each call? If you practice encapsulating your code, you'll never really "know" if a certain library has been referenced without adding additional overhead and duplicate code throughout your app. I know there are some very clear examples of when to do this, but what about the vast majority of UDFs that only get called 20% of the time. I guess it's a matter of six of one and half dozen of the other. Sean, since you mentioned this above, do you have any recommendations to accomplish only calling the necessary function libs? Does Mach-ii have any inherent abilities for elegantly handling UDFs and what-not, or is it still left up to the developer? Tyler --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.768 / Virus Database: 515 - Release Date: 9/22/2004 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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]
