> Pet peeve: *shared* scopes (Hal Helms defines "persistent" > as "it's still there after you switch the computer off" > and I agree with him - scopes are not persistent, databases > and files are persistent!).
The problem with pet peeves is that they're often hard to justify logically. I have yet to see a real definition for "persistent" that would rule out its use to describe CF memory variables. I guess it depends on how you define the program that's running - I tend to think of each individual .cfm file as a separate program, so if something lasts beyond its scope, it's "persistent". Also, I wasn't aware that the Session scope is shared. 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 Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm