Actually, this is the Allaire recommendation for 4.01 and prior. For 4.5,
they recommend using the new scope attribute, as in:
scope="application"
or
scope="session"
which results in the same behavior. For more see Knowledgebase Article
14165.
> -----Original Message-----
> From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> Good answer... makes sense... officially it conflicts with Allaire's
> recomendation, but I think you are correct.
>
> -Cameron
>
> --------------------
> Cameron Childress
> McRae Communications
> 770.460.7277 x.232
> 770.460.0963 fax
>
> > -----Original Message-----
> > From: David Gassner [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 29, 2000 4:01 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Using CFLOCK
> >
> >
> > session.sessionid is a value which is set by the CF server, not
> > by the user,
> > and is based on the CFID and CFToken cookies. It's initialized at the
> > beginning of the session, and not changed until the session expires, and
> > therefore (theoretically) it needs no locking.
> >
> > Doing it this way simulates the rules followed by CF server 4.5 when you
> > turn on "Automatic read locking" in CF Server Administrator.
> >
> > > -----Original Message-----
> > > From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, March 29, 2000 11:54 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Using CFLOCK
> > >
> > >
> > > So David... riddle me this...
> > >
> > > If you should lock all session vars, and you name your lock
> > with a session
> > > var, what is locking the session var you are using as the name of
> > > the lock?
> > >
> > > -Cameron
> > >
> > > --------------------
> > > Cameron Childress
> > > McRae Communications
> > > 770.460.7277 x.232
> > > 770.460.0963 fax
> > >
> > > > -----Original Message-----
> > > > From: David Gassner [mailto:[EMAIL PROTECTED]]
> > > > Sent: Wednesday, March 29, 2000 2:31 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: RE: Using CFLOCK
> > > >
> > > >
> > > > If you are locking session vars, use the name:
> > > >
> > > > name="#session.sessionid#"
> > > >
> > > > If you are locking application vars, use the name:
> > > >
> > > > name="#application.applicationname#"
> > > >
> > > > > -----Original Message-----
> > > > > From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> > > > > Sent: Wednesday, March 29, 2000 10:48 AM
> > > > > To: [EMAIL PROTECTED]
> > > > > Subject: RE: Using CFLOCK
> > > > >
> > > > >
> > > > > > When using CFLOCK how important is it to name the lock
> > > > >
> > > > > In CF 4.0: very, always name it... In CF 4.5, which I am not
> > > > > using yet, I am
> > > > > uncertain if names should be used or not. In 4.5, I *think* they
> > > > > should be
> > > > > used in all cases except for when locking application, session
> > > > and server
> > > > > vars. Someone else should be able to answer that for you.
> > > > >
> > > > > > and if you name all locks should everylock in your application
> > > > > > have a different name?
> > > > >
> > > > > Depends on what you are locking and why you are locking it.
> > > > >
> > > > > -Cameron
> > > > >
> > > > > --------------------
> > > > > Cameron Childress
> > > > > McRae Communications
> > > > > 770.460.7277 x.232
> > > > > 770.460.0963 fax
> > > > >
> > > > > ------------------------------------------------------------------
> > > > > ------------
> > > > > Archives: http://www.eGroups.com/list/cf-talk
> > > > > To Unsubscribe visit
> > > > > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf
> > > > _talk or send a message to [EMAIL PROTECTED] with
> > > > 'unsubscribe' in the body.
> > > >
> > > > ------------------------------------------------------------------
> > > > ------------
> > > > Archives: http://www.eGroups.com/list/cf-talk
> > > > To Unsubscribe visit
> > >
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
> > send a message to [EMAIL PROTECTED] with
> 'unsubscribe' in
> > the body.
> >
> > ------------------------------------------------------------------
> > ------------
> > Archives: http://www.eGroups.com/list/cf-talk
> > To Unsubscribe visit
> > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf
> _talk or send a message to [EMAIL PROTECTED] with
> 'unsubscribe' in the body.
>
> ------------------------------------------------------------------
> ----------
> --
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
>
> ------------------------------------------------------------------
> ------------
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
