---------- Original Message ----------------------------------
from: Ken Beard <[EMAIL PROTECTED]>
>can you still use the name attribute in 5.0? Sometimes it's nice to have a
>higher level of control.. rather than having to use scope="application".
>don't want my app to break when we upgrade. anyone know?
We ran name="#session.sessionID#" locks when we moved from 4.5 to 5.0 and it appeared
to work fine. The official Allaire/MM stance is to use scope locking not name locking
(at least for server,application, & session variables).
I'm feeling rather cynical right now, so I wonder if scope locking isn't chosed as
safer - lock the entire scope rather than lock by unique name.
Personally I'm tired of locking, throwing on locks timeouts, auto-read-locking not
catching non-cfset reads (anybody else know that)...
we're moving to client variables.
Chris Norloff
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
