So... what about persistance... which internal variables persist from one
request to the next?
First off, let's define "persistence". Hal Helms has a great definition: it's persistent if I can turn off my computer, come back later and it's still there.
So, let's not talk about "persistence" when we really mean shared scopes.
Any changes with CFMX 6.1?
Not really. Instance data in a CFC has a lifetime equal to the scope in which the CFC itself exists. A CFC instance created by a simple cfinvoke 'dies' at the end of the cfinvoke (unless the CFC instance is returned by the call and assigned to a longer-lived variable). Otherwise a CFC instance in page scope exists for the execution of that page, in request scope exists for the execution of that request, in session scope for the session, in application / server scope until the server is restarted.
Inside a CFC, there are two scopes: "this" (public instance data) and "variables" (non-public instance data). The unnamed scope still exists and, as in regular CF pages, corresponds to the "variables" scope. These two scopes exist for the lifetime of the CFC instance itself.
Inside a function, there are two additional scopes: "arguments" (for the arguments!) and "var" for true local variables. Both of those scopes exist for the execution of the function only (and are recreated on the next execution of each function).
Does that provide enough information?
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
