And just to add Dave, that there are a lot of people that tend to think that they can do everything in CF and sure there hasn't been anything I can't do with CF. However there are many times when CF is not capable and it takes a good developer to know the limitations of CF, I had a bit of code that took something like 4 hours to run under CF but because of budget and constraints I had to try, I didn't realize at the time that if something went wrong it meant running this again. After the 2nd failure I ended up writing a com object to help out and the work was done in 10 minutes instead of 4 hours. And all it was doing was pulling records out of the DB modifying the data and putting it back in. But CF had problems with the number of records it could process in one hit, where as the com object had no problems and is still working after 4 years.
SO this is a good thing to keep in mind as well for the newer CF developers out there. -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Friday, 9 November 2001 8:37 AM To: CF-Talk Subject: RE: Session variables > Either way, since that call I haven't seen a real reason to > go back to using the application scope unless I really need it. > > I realize that a lot of people will email me saying, "Use the > application scope, that's what it was meant for." I really don't > know what to say to that. The truth is that the Application > scope was created for persistent variables that run true over > the whole program, but I'm rather happy with the performance > gains and I'm also happy about not having to lock my variables > all the time. I think you hit the nail on the head - don't use something unless you really need it. There are legitimate uses for the Application scope. Setting constants (DSNs, file paths, etc) within the Application scope is likely to be more trouble than it's worth. It's important to realize that every choice you make as a programmer has pros and cons, and in some cases the pros will outweigh the cons while in other cases they won't. There's rarely something that's always the right choice. This kind of echoes the Flash discussion earlier this week - in some cases, Flash is a good choice, and in other cases, it isn't. What's more, it's up to us programmers to figure out the right choices - that's really the hard part of programming; writing code after you've made those choices is usually pretty easy. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
