Cold Fusion Programming

All programming languages have an associated learning curve, and ColdFusion is not an exception to that. However, training time is less than with several other languages. This means the student gains competence and confidence in a shorter time period.

Here are a very few examples of the basics. A rule of thumb is never to use words reserved in other protocols for naming ColdFusion variables. Also, be consistent with case throughout, even though CF is not case-sensitive. It's a good habit to get into with ColdFusion. Some new programmers resist using descriptive terms for variables, but "old timers" know the value of descriptions when they have to debug a program. Adding the context to a variable in the code, resulting in a scope, avoids potential conflicts between variables.

Many more rules apply and must be learned, of course. A primary avoidance goal is that of not crashing the CF application server. The server can and does crash when multiple threads are trying to access the same variable all at the same time. Solutions include spare use of exclusive locking (except where it's mandatory) and frequent use of Read Only locks. To avoid collisions, however, a great deal more needs to be taken into consideration before locks are used. It's recommended that training steps be followed in sequence, not slammed through as unimportant or leapfrogged.

Books About ColdFusion

As with other languages, after-market books written by experts vary in their approach, even though the gurus all know their stuff. A little humor always helps when it's mixed in with true knowledge. A dozen or more ColdFusion books are currently available. The O'Reilly series, for example, contains a detailed volume on programming ColdFusion. There's even a ColdFusion for Dummies.