Yep.they are all wrapped nice and tight in CFTRY and CFCATCH statements.
I can see I have to spend a good bit of time in the future analysing this
code and learning it.
-Gel
-----Original Message-----
From: Michael Smith [mailto:[EMAIL PROTECTED]]
In addition to removing the NAME parameter when using SCOPE the type for
reading variables is READONLY and not EXCLUSIVE. Also if they are using
THROWONTIMEOUT is there a CFTRY wrapped around this somewhere in case it
does timeout? :-)
- Michael Smith, TeraTech, Inc http://www.teratech.com/
Mark Stewart wrote:
> gel,
>
> Whoever wrote the code probably got the idea from the Mastering ColdFusion
4.5 book. The book uses that syntax quite often. However, I've never seen
the scope attribute used in conjunction with the name attribute. That's
being redundent, redundent. You know what I mean? You know what I mean? :-)
>
> I will admit that I've used the name="#session.sessionid#" before and had
no problem with it - as long as sessionmanagement is enabled, doh! Now that
I'm all grown up, I use the scope attribute. Why? Peer-pressure I guess.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
