sorry, I think I may be misunderstanding you. if you have a variable in a shared scope:
session.myvar then you need to lock and read/write access to it. > -----Original Message----- > From: Robertson-Ravo, Neil (REC) > [mailto:Neil.Robertson-Ravo@;csd.reedexpo.com] > Sent: 17 October 2002 11:32 > To: '[EMAIL PROTECTED]' > Subject: RE: [ cf-dev ] Good/Bad? > > > thats poppycock :-p, > > If you have copied the session scope into the request scope > and you are > referencing your session vars as : request.session.myvar you > do not have > lock AFAIK > > you just have to copy the back into the session scope. > > N > > -----Original Message----- > From: Rich Wild [mailto:r.wild@;e-mango.com] > Sent: 17 October 2002 11:15 > To: '[EMAIL PROTECTED]' > Subject: RE: [ cf-dev ] Good/Bad? > > > you need to lock all shared scope variable access. can't get > away from it. > > > -----Original Message----- > > From: Robertson-Ravo, Neil (REC) > > [mailto:Neil.Robertson-Ravo@;csd.reedexpo.com] > > Sent: 17 October 2002 11:25 > > To: '[EMAIL PROTECTED]' > > Subject: RE: [ cf-dev ] Good/Bad? > > > > > > so, all in all; the code I posted is wrong (in that it > doesnt actually > > alleviate the fact you need to lock!) > > > > -----Original Message----- > > From: Rich Wild [mailto:r.wild@;e-mango.com] > > Sent: 17 October 2002 11:01 > > To: '[EMAIL PROTECTED]' > > Subject: RE: [ cf-dev ] Good/Bad? > > > > > > I used this method once - Russ suggested an idea for a tag > > that accepts a > > list of variable names and then it copies all the those that > > exist in the > > session scope into the request scope. > > > > I made it into a tag and it worked brilliantly, so that on > > each page I only > > needed to name the session or app vars that I needed > copying into the > > request scope for that page. > > > > eg: > > > > <cf_apptap vars="myvar1,myvar2,myvar3" scope="session"> > > > > would copy session.myvar1, session myvar2 and session.myvar3 into > > request.myvar1 etc etc. > > > > on another page you might only need to request.myvar1 so you > > would just do: > > > > <cf_apptap vars="myvar1"> > > > > it saved duplicating everything all the time. > > > > > -----Original Message----- > > > From: Taz -=TT=- [mailto:chris@;cfmaster.co.uk] > > > Sent: 17 October 2002 11:09 > > > To: [EMAIL PROTECTED] > > > Subject: Re: [ cf-dev ] Good/Bad? > > > > > > > > > > > > > > > > > > > Thanks guys you have confirmed what I thought : it is > all over the > > > > place...the system is very poor and indeed needs a rewrite > > > but thats not > > > on > > > > the cards. > > > > > > > > what needs to be done is to copy the session variables into > > > the request > > > > scope to avoud locking them.... > > > > > > > > its a nightmare, it really is! > > > > > > Its not a bad thing to do... I tend to use this approach when > > > using session > > > variables instead of client. But I've never had so many that > > > I needed to > > > loop through all values in the scope. Usually I just stick a > > > few duplicate > > > ops in the app_globals.cfm > > > > > > <cflock ...blah...> > > > <cfscript> > > > Request.Whatever = Duplicate(Session.Whatever); > > > ... > > > ... > > > </cfscript> > > > </cflock> > > > > > > Of course you have to remember to write to the session scope > > > when you change > > > the values, but its way better to do it this way than > > > constantly locking > > > session read ops. Same goes for application scope if you're > > using it. > > > > > > Taz > > > > > > > > > -- > > > ** Archive: > http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > For human help, e-mail: [EMAIL PROTECTED] > > > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
