On 5/21/01, Jim McAtee penned:
>So it sounds like CF 5 promises to be just as unstable when used in an
>environment with inexperienced developers. Most notably, shared hosting
>setups.
That's where the forced locking comes in. They added that so
inexperienced developers are FORCED to lock all the memory resident
variables, if the host so chooses.
Let's just pray to the heavens that they didn't change it drastically
and break all our 4.5 applications like they broke 2 years worth of
my 4.0 apps when 4.5 came out. Heck, I own 4.5 and still haven't been
able to install it on my server because I've been spending spare time
during the past 6 months fixing all my 4.0 apps to work on 4.5. I'm
NEVER gonna forgive Allaire for that snafu. Cost me thousands. I'm
probably gonna end up installing 5.0 before I get a chance to install
my copy of 4.5.
The best bet is still to steer as far clear of memory resident
variables as possible and stick with client variables.
--
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
