The default cache size for generated charts is 50 (the 50 most recent charts, after which the oldest is dropped from the cache). If you generate lots of charts (and are caching to disk) you may want to increase the cache size to prevent unnecessary chart regeneration. (Applies to: ColdFusion MX)
charts can be cached for improved performance (if the same chart if requested it can be served from the cache instead of being regenerated). The default cache is disk based, but for greater performance the cache can be stored in memory (this option is set in the ColdFusion Administrator). Only move...
The ColdFusion MX charting engine is multi-threaded allowing it to generate multiple charts concurrently if needed. If you only use sporadically you can set the thread count (in the ColdFusion Administrator) down to 1 to reduce memory load. (Applies to: ColdFusion MX)
Need to upgrade ColdFusion MX from a trial or developer edition to a full license? You do not have to reinstall or even restart the software. Instead, go to the Version Information page in the ColdFusion Administrator and you'll be able to enter license information (a serial number) which can be...
Need to know where ColdFusion is installed? Check the SERVER.ColdFusion.Rootdir variable which will contain the path to the ColdFusion root directory. (Applies to: ColdFusion MX)
ColdFusion MX runs on top of a J2EE server, and to find out exactly which one is being used check the SERVER.ColdFusion.AppServer variable (if using standalone ColdFusion the value will be JRun4). (Applies to: ColdFusion MX)
CFC methods generally do not generate output, rather, they return data. As such, it is advisable to suppress method output so that white space is not created and output is not generated inadvertently. To suppress method output set OUTPUT="no" in the call. (Applies to: ColdFusion MX)
Arguments (parameters) passed to (when invoking CFC's or Web Services) are usually passed in NAME=value pairs. But if you need to build your arguments programmatically, here is another option - create a structure (with the StructNew() function) and populate it with all the arguments (using the...
Converting an application that uses ColdFusion sessions to use J2EE sessions? Be careful. If your code ever refers to SESSION.CFID or SESSION.CFTOKEN directly that code will break (as those variables do not exist in J2EE sessions). SESSION.URLTOKEN and SESSION.SESSIONID, however, do exist in J2EE...
ColdFusion SESSION variables use two cookies (named CFID and CFTOKEN) to identify clients. These persist even after a browser is closed, and so ColdFusion sessions can remain active even if a browser is closed and then reopened. J2EE sessions terminate when a browser closes, so if you need this...