I would have to agree. Sometimes the Allaire DOCs are not always up to
snuff. As far as locking goes. Lock it. If you have any doubt lock the
variable. For reading writing anything. There have been several long
ranging threads on this board on how important locking variables is.
Kevin Schmidt, Web Technology Manager
Allaire Certified Cold Fusion Developer
pwb inc.
integrated marketing communications
350 S. Main St., Suite 350
Ann Arbor, MI 48104
734.995.5000 (tel)
734.995.5002 (fax)
www.pwb.com
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 10:08 PM
Subject: CF 4.5.1 SP2 Problems
> We had a major instability problem with CF 4.5.1 SP2 on NT.
>
> We flew in an Allaire consultant who had us put in tons of
> CFLOCK statements and things got better. However, I feel that
> it is extremely important for you guys to know, that there is not
> a single example in the CFDOCS Examples, which come with
> the product, which has CFLOCK statements correctly installed.
>
> We found out the hard way, that you need to use CFLOCK
> statements profusely throughout, but it is unbelievable to me
> to look through all the examples in the CFDOCS folder, and
> see poorly written CF code. For that matter, just start running
> lots of those examples, under load, and you will see problems.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
