stems, EDS
> [EMAIL PROTECTED]
>
>
> -Original Message-
> From: JB Mentzer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 16, 2001 9:25 PM
> To: CF-Talk
> Subject: Re: Any horror stories from not locking session vars?
>
>
> Hi all
>
> "[EMAIL P
Sent: Thursday, August 16, 2001 9:25 PM
To: CF-Talk
Subject: Re: Any horror stories from not locking session vars?
Hi all
"[EMAIL PROTECTED]" wrote:
> A further suggestion is to avoid SESSION, APPLICATION and SERVER
> variables completely. Build a site that will be ready for
&g
Developer
Australia New Zealand Food Authority
Boeing House
55 Blackall Street
BARTON ACT 2600
Ph: +61-2-6271 2256
Fax: +61-2-6271 2278
http://www.anzfa.gov.au
-Original Message-
From: JB Mentzer [mailto:[EMAIL PROTECTED]]
Sent: Friday, 17 August 2001 12:25
To: CF-Talk
Subject: Re: Any horror st
Hi all
"[EMAIL PROTECTED]" wrote:
> A further suggestion is to avoid SESSION, APPLICATION and SERVER variables
> completely. Build a site that will be ready for loadbalancing WITHOUT
> sticky sessions now and don't even fool with server specific shared memory
> scopes.
So what variables am I t
Allaire article from the Reference Desk entitled ColdFusion Locking Best Practices:
http://www.allaire.com/handlers/index.cfm?id=17318&method=full
>From the CF instruction manual:
http://www.allaire.com/cfdocs/Administering_ColdFusion_Server/03_Configuring_ColdFusion_Server/admin0312.htm#105960
> > You can use the classic "ATM machine" example typically used to
> > explain concurrency and basic transactional logic.
>
> Is that the one where the client spends all his time at the ATM
> withdrawing money to pay you to fix the site? ;-)
If that example works well enough to convince the c
> You can
> use the classic "ATM machine" example typically used to
> explain concurrency
> and basic transactional logic.
Is that the one where the client spends all his time at the ATM
withdrawing money to pay you to fix the site? ;-)
~~
Struc
Zac -
LOL
and would the appropriate breakfast be "Locks" and bagels
-Ben
-Original Message-
From: Zac Belado [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 2:24 PM
To: CF-Talk
Subject: RE: Any horror stories from not locking session vars?
At 04:44 PM 8/6/2001
At 04:44 PM 8/6/2001 -0400, you wrote:
>LOCK LOCK LOCK is all i can say!
Must make dinner conversations very repetitive.
~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http:
2001 3:44 PM
> To: CF-Talk
> Subject: RE: Any horror stories from not locking session vars?
>
>
> > I have been asked to do a code review of a site and I have
> > found that the developers don't bother to lock session variables
> > when then read or write them
> So, what you are saying is put a lock around ALL thing
> regarding Session variables (Read, write, etc)?
Yes, that's what you want to do.
Very often, if you don't do this, an application will work fine during the
limited testing that happens during development, but once it's put under
load, i
LOCK LOCK LOCK is all i can say!
-Original Message-
From: Don Vawter [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 10:11 AM
To: CF-Talk
Subject: Any horror stories from not locking session vars?
I have been asked to do a code review of a site and I have found that the
develo
So, what you are saying is put a lock around ALL thing reguarding Session
variables (Read, write, etc)?
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 3:44 PM
To: CF-Talk
Subject: RE: Any horror stories from not locking session vars?
>
> I have been asked to do a code review of a site and I have
> found that the developers don't bother to lock session variables
> when then read or write them. Does anybody have an good horror
> stories about the dangers of doing this so I legitimately show
> the customer why this is a problem
-- Original Message --
from: "Don Vawter" <[EMAIL PROTECTED]>
>I have been asked to do a code review of a site and I have found that the
>developers don't bother to lock session variables when then read or write
>them. Does anybody have an good horror storie
Somewhat related: is there any reason to do locking when you're only
*reading* from application variables?
> -Original Message-
> From: Don Vawter [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 06, 2001 10:11 AM
> To: CF-Talk
> Subject: Any horror stories from not locking session var
Sure, I inherited one.
It was a Customer Service application where the customer's unique
identification number was a session variable. The application made heavy
use of frames to split information along the lines of "current" and
"historical" activity.
Needless to say there were more than one C
Reasons to CFLOCK shared memory scopes:
1.) Allaire/Macromedia ( the company that made the Application server ) says
to.
2.) I have personally seen strange, un-diagnosable errors that really could
not be pinned to anything. Corrupt memory or PCODE and everything goes bad.
Maybe CFLOCKing would fi
18 matches
Mail list logo
