> > Wherever there were perfomance issues they always related > > back to bad coding or dodgy infrastructure. > > Not always true. CFHTTP, the dodgy locking in 4.0, CFFILE > all were tags that, even if you coded properly, liked to die. > Did I mention CFHTTP?
You neglected CFOBJECT/COM, which never worked all that well in CF (compared to ASP, for example), and you really oversimplified the "dodgy locking" - CF 3 gave us memory variables but no way to lock them at all! Good times, good times ... Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Host with the leader in ColdFusion hosting. Voted #1 ColdFusion host by CF Developers. Offering shared and dedicated hosting options. www.cfxhosting.com/default.cfm?redirect=10481 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
