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.
>
> Mark Stewart
> Programmer/Analyst
> Communication Concepts
> 215.672.6900 x1332
>
> >>> [EMAIL PROTECTED] 04/09/01 04:23PM >>>
> Thanks..that's what I thought..only thing that made sense was if it was an
> autogenerated variable..and the only ones I know of are cftoken and cfid
> right.
>
> So apparently the little murbin furbin that wrote the app in fusebox
> 'forgot' to include that.
>
> At any rate, I don't think I did anything terribly wrong by hardcoding a
> name for the CFLOCK...it was easier than racking up hours I wasn't getting
> paid for by changing each CFLOCK individually..especially since there was no
> CFSTUDIO and I was operating 'blind' in Notepad ;-)
>
> The statement actually looked something like this
>
> <CFLOCK name="#session.sessionid#" SCOPE="Session" Throwontimeout="yes"
> type="EXCLUSIVE">
>
> And then the statements to read some variables were here..
>
> </CFLOCK>
>
> The default timeout value I think is 20 minutes, and that should be just
> fine for their current needs.
>
> Thanks for the response though!
> Much appreciated!
>
> -Gel
> www.carigamer.com
> Our Gamers DO Wear Thongs!
>
> -----Original Message-----
> From: Michael Smith [mailto:[EMAIL PROTECTED]]
>
> Gel
> I think folks usually create session.sessionid equal to session.cftoken +
> session.cfid in the application.cfm
>
> I would suggest using CFLOCK SCOPE="SESSION" rather than named locks as then
> you can turn on the CF admin strict
> lock checker to be sure all session vars are locked.
>
> Also I am not certain that if a session var appears in the CFLOCK tag
> itself, rather than between the <CFLOCK> and
> the </CFLOCK> that it is really locked...
>
> If you don't have any structures or queries in the session vars it would be
> best to convert to client vars (stored
> in database rather than registry) as these don't need locks at all...
>
> See http://www.cfug-md.org/articles/locking.cfm for more info.
>
> - Michael Smith, TeraTech, Inc http://www.teratech.com/
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
