Folks,
NOTE: This message probably affects you, even if you don't use Plum's Verity
features.
I just found a small issue with the Plum Framework's testing for existing
objects. We made a last-minute change to the Verity code in Plum just
before it was released, and everything regression tested just fine so we
didn't see that there was any problem to solve, but a recent test of Verity
in a site we're developing showed that, on every request, Plum
reinstantiates the Verity collections document that we cache in memory.
While this doesn't effect functionality in the slightest, it does make each
request take slightly longer than necessary.
Here's the fix.
Look for this section of code in Global.cfm:
<cfif NOT IsDefined("Application.collections")>
<cfinvoke
component="#Application.Verity#"
method="CreateCollectionsObject">
<cfinvoke
component="#Application.Verity#"
method="CreateCollectionCheckboxes">
</cfif>
and change the CFIF test to:
<cfif NOT IsDefined("Application.collectionsObject")>
You should see an increase in speed on every request after you make this
modification.
*** MAKE SURE *** to thoroughly test everything Verity-related in a staging
environment before deploying to production!
Hope this helps.
Respectfully,
Adam Phillip Churvis
Certified Advanced ColdFusion MX 7 Developer
http://www.ProductivityEnhancement.com
Download Plum and other cool development tools,
and get advanced intensive Master-level training:
* C# & ASP.NET for ColdFusion Developers
* ColdFusion MX Master Class
* Advanced Development with CFMX and SQL Server 2000
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
