Nando, thanks very much. This helps a lot. I have a couple of questions about your response or clarifications to my original questions: > On 3/6/07, Joe Lakey <[EMAIL PROTECTED] > wrote: > > > 1. I use CFC instances in persistent scopes--mostly > > session--and create > > a unique named lock inside each instance. > > > Is there a specific reason you are using a lock? Ordinarily, > this isn't needed ... but i don't understand your use-case. >
Suppose I do <cfset Session.user = CreateObject( "component", "UserCFC" ).init( dsn=Application.DSN, scope="Session" ) > do I need to lock the session scope when calling a method of Session.user? I expect to have multiple concurrent users (hopefully). Isn't there a danger of some kind of session overlap if calls to Session.user's methods aren't locked? There's probably a better technical term for what I mean by "overlap"--a user's actions affecting another user's session in some unintended way. > > If you then do > > > > cfset variables.object1 = arguments.object1 > > > > you can use object1 anywhere within object2 > > 5. If a CFC (FirstCfc) property is a reference to > another object > (SecondCfcInstance), can SecondCfcInstance "see" the FirstCfc's > properties and methods? > > > Don't quite get this question ... In your example above, after you do cfset variables.object1 = arguments.object1 inside object2 so that you can use object1 within object2, is the inverse true, i.e. can object1 now see object2's methods? Thanks again, Joe You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
