Setting commonly used functions to a 'permanent' memory scope such as server
or application is a good idea. A better one would be to create a CFC that
contains the common functions as well as common data and store that CFC in
the memory scope.
How would that work under a clustered environment?
fax
www.nylontechnology.com
Vote for Pedro
-Original Message-
From: Ryan Duckworth [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 06, 2005 5:54 PM
To: CF-Talk
Subject: cfscript Common Functions and Best Practices
Currently we have many functions that we use within cfscript. We
6 West 14th Street
New York, NY 10011
212.691.1134
212.691.3477 fax
www.nylontechnology.com
Vote for Pedro
-Original Message-
From: Ryan Duckworth [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 06, 2005 5:54 PM
To: CF-Talk
Subject: cfscript Common Functions and Best Practices
]
Sent: Wednesday, December 07, 2005 9:06 AM
To: CF-Talk
Subject: Re: cfscript Common Functions and Best Practices
Just so you know, you can also use COAL to do something similar.
You just create an object out of COAL, and then you can access your
different libraries at the time you need them
-
From: Ryan Guill [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 07, 2005 9:06 AM
To: CF-Talk
Subject: Re: cfscript Common Functions and Best Practices
Just so you know, you can also use COAL to do something similar.
You just create an object out of COAL, and then you can access
Message-
From: Ryan Guill [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 07, 2005 9:39 AM
To: CF-Talk
Subject: Re: cfscript Common Functions and Best Practices
You do not have to put the files outside of the current application or
have any mappings if you dont want. You certainly can if you
No problem, let me know if you have any questions.
On 12/7/05, Ben Nadel [EMAIL PROTECTED] wrote:
Ryan,
I appreciate the response. I am definitely interested in at the very least
taking a look at how it works, as I am very new to OOP and very interested
in how you all get things working at
Currently we have many functions that we use within cfscript. We are
storing them in the request scope (see 2 examples below).
Here is what I am don't like about this approach: Every page hit from
every user is loading these common functions. I personally am not
convinced that the request
Setting commonly used functions to a 'permanent' memory scope such as server
or application is a good idea. A better one would be to create a CFC that
contains the common functions as well as common data and store that CFC in
the memory scope.
Currently we have many functions that we use
Hartsfield
http://acoderslife.com
-Original Message-
From: Ryan Duckworth [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 06, 2005 5:54 PM
To: CF-Talk
Subject: cfscript Common Functions and Best Practices
Currently we have many functions that we use within cfscript. We are
storing them
10 matches
Mail list logo
