On 6/20/05, Johnny Le <[EMAIL PROTECTED]> wrote: > When people say "shared scope variables" or "persistent scope variables", do > they mean exactly the same thing or is there a difference in definitions > between "shared scope variables" and "persistent scope variables"?
<rant> This is one of my pet peeves about CFers... The classic IT definition of persistent means: if you switch off your system and switch it back on, the data is still there. Client variables might just squeak into that definition but the other shared scopes certainly do not! I don't know quite where the idea came from that these scopes were "persistent" (no doubt early Allaire documentation?) but the mis-use has persisted (sic) unfortunately... In an effort to get CF taken more seriously by other IT professionals, I try to jump on this mis-use of terminology every time I see it... </rant> Databases are persistent, memory is not. Both databases and memory can be shared, however. -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:210048 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
