I don't agree at this point with putting libraries "IN" CFCs. There are CFTags, CFCs and UDF Libraries.
I wrote a custom UDF Library handler, that puts the libraries into "request" scope... that way the libraries don't get outdated. It also checks to see if the library has been called, and if it is the correct version of the library. It is sort of include on the style of the old C programming I did before C+. This means each library can only be called once, it's instantiated as a request scope... and the libraries can be updated, used or called from anywhere! (Without conflicts... and they don't seem to have a real hit on MX for speed to call multiple or large libraries... haven't done stress testing... because I am targeting my solutions for the SOHO market... but I think they have enterprise potential to scale also.) John Farrar SOSensible ---------------------------------------------------------- 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]
