Cliff:
> (1) Use the variables scope for instance variables to prevent access from
> outside the object, and
> (2) Use the function local scope ("var") to make sure that the objects are
> thread safe.
thats correct
> Can someone explain what kinds of problems emergy if I were - for example -
> to > do a cfquery inside one of my methods using a name attribute hadn't
> already
> been created as a function local scoped variable?
i'm pretty sure (someone please correct me if im wrong here...) that
unnamed variables of any type go into the variables scope of the
instance (at least). this allows any other method access to those
variables. as a practice i do specifically "var" my variables if not
needed outside of the method call to prevent any leakage. also i tend
to use similar if not identical variable names everywhere so that
could be a problem elsewhere.
> Also, are there any concerns/requirements for locking method calls when an
> object is stored in a persistent scope?
someone else will have to answer this one :)
hope that helps,
jeff
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
