Some of the dangers to this approach include: the amount of memory
allocated to the JVM. If you stuff alot of data into the Application scope,
it persists in the JVM allocated memory and it's not available to the rest
of the system/application.
You really can't change data in the Application
For what it's worth, the approach of storing a global data item in the
application scope seems to be legit according to the documentation. Here's what
it said in the CF10 doc:
Application variables are a convenient place to store information that all
pages of your application might need, no
+1
On Thu, Jan 29, 2015 at 12:53 PM, Russ Michaels r...@michaels.me.uk wrote:
I'll add for the sake of brevity, please don't put application wide cfcs in
session scope, as a hosting provider I have seen this kill a server. 5000
users = 5000 instances of the cfc.
In most cases using a
I'll add for the sake of brevity, please don't put application wide cfcs in
session scope, as a hosting provider I have seen this kill a server. 5000
users = 5000 instances of the cfc.
In most cases using a mapping solves the issues you have with cf not
finding the cfc.
On Thu, Jan 29, 2015 at
4 matches
Mail list logo
