If possible, I would put the functions in a CFC, then store the CFC in
the Application scope. That would keep them in memory.
If you have other CFCs that might use the UDF CFC, you can pass a
reference to the necessary methods.
<cfset Application.Functions = CreateObject("component", "UDFs")>
...then...
<cfset myReturnVar = myMethod(Application.Functions, "myOtherArg")>
M!ke
-----Original Message-----
From: Ian Sheridan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 9:07 AM
To: [EMAIL PROTECTED]
Subject: [CFCDev] UDF in a CFC or Include?
I am at a quandary right now weather or not I should place my UDFs in an
include or a CFC. What do most of you do? Is there a difference if you
you either place the included UDFs in the request scope or place the CFC
in the app/session scope?
Right now I have gone CFC crazy and placed them in one. But I have an
app that is going to be used eventually by thousands of people a day
(intranet) and possibly across the country (extranet). SO I am looking
at ways to make this thing much more efficient.
Regards,
Ian
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ian Sheridan
[EMAIL PROTECTED] http://www.savagevines.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
----------------------------------------------------------
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]
----------------------------------------------------------
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]
