> What I need to know is has anyone else experienced such an 
> issue and, if so, how was it resolved (other than search and 
> replace)?

Unfortunately for you, that is the only correct (and adequate) resolution in
most cases. I've run into this issue with several applications I've had to
fix, and that was the only solution. Fortunately, it's an easy solution. You
don't need to do a big search and replace to get the initial fix - just
remove the Duplicate function:

<cfset Request.AppGlobal = Application>

Sometimes, what works well with one version of CF doesn't work well with
another. In CF 5 and earlier, it was very important to use CFLOCK to prevent
concurrent access to memory variables; failure to do this would often cause
the server to fail spectacularly under load. Rather than pepper their code
with CFLOCK tags, many CF programmers would use Duplicate to copy
Application and Session scopes into Request at the top of their pages, and
copy them back at the bottom. Unfortunately, this is a very expensive thing
to do, especially if you have a lot of stuff in those scopes.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/

Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257009
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to