I would opine that locking shared scope variables is still a best practice and not locking shared scope variables is a bad practice, regardless of CF version.

- Calvin
  ----- Original Message -----
  From: Samuel R. Neff
  To: CF-Talk
  Sent: Monday, October 27, 2003 5:13 PM
  Subject: RE: Scope Locking (RE: Blue Dragon and Fusebox)

  You don't need to lock in MX (or I guess BD) to protect against corruption
  or crashing.

  You do still need to lock to protect against race conditions.

  More info here:

  http://www.macromedia.com/support/coldfusion/ts/documents/tn18235.htm

  HTH,

  Sam

  -----------------------------------------------
  Blog: http://www.rewindlife.com
  Charts: http://www.blinex.com/products/charting
  -----------------------------------------------

  > -----Original Message-----
  > From: Haggerty, Mike [mailto:[EMAIL PROTECTED]
  > Sent: Monday, October 27, 2003 9:53 AM
  > To: CF-Talk
  > Subject: Scope Locking (RE: Blue Dragon and Fusebox)
  >
  > Matt -
  >
  > I wanted to confirm what you mean when you say 'the
  > application scope is now automatically synchronized'.
  >
  > Does this mean locking the application scope is unnecessary
  > in CFMX & BD, even when setting values? Or am I just
  > misunderstanding your comments.
  >
  > M
  >
  > -----Original Message-----
  > From: Matt Liotta [mailto:[EMAIL PROTECTED]
  > Sent: Friday, October 24, 2003 11:44 PM
  > To: CF-Talk
  > Subject: Re: Blue Dragon and Fusebox
  >
  > ...
  > Now that issue I have seen before. First, you don't need to
  > use such a technique with BlueDragon or even CFMX since the
  > application scope is now automatically synchronized.
  > ...
  >
  > Matt Liotta


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to