> 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]
