CFInternals

Cache structs, not queries.

Thus far I've helped install two of the largest ColdFusion-based content management systems for two different clients, and in comparing both one thing is evident: they both just love structs.

More on Named Arguments

Over on Peter Bell's blog he wrote the article that I was going to write on The Benefits of Named Arguments When Calling CFC Methods, thus saving me the trouble (Thanks Peter). However, I would like to add another interesting way to use them, and that's the topic of this post.

Sometimes, making an assumption is a good thing... redux.

This is a repost of the Sometimes, making an assumption is a good thing... article, where I talk about the "Assumed Existence" pattern and its place in multi-threaded systems.

Turns out that FeedBurner doesn't like displaying code in the summary. Who knew?

Sometimes, making an assumption is a good thing...

How often have you seen (or written) code like the following:

<cffunction name="getProductInfo" returntype="struct">
  <cfargument name="sku" type="string">
  <cfif not structKeyExists(application.products,arguments.sku)>
    <cfset application.products[arguments.sku] =
      this.loadProductInfo(arguments.sku)>
  </cfif>
  <cfreturn application.products[arguments.sku]>
</cffunction>

Typical "if it doesn't exist make one" test, right? Now, how many people know that under the right circumstances, this function can blow up with an error?