> Yes but during that test were those variables being written to at
> the same time? I beleive that if you do a read without locking,
> and a write occurs or is occuring at the same time, you will have
> problems.
>
> But what if there is no writing? Say you setup a datasource name if
> its not d
say, there is a cool regex example in Ben's "Advanced Cold Fusion (Green)"
book dealing with
ParamaterExists()
Anyone want to build one for Locking?
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To
I agree. The article claims they don't automate locking for
(1) performance issues. Well, if I do all the same locks by hand the
performance will be WORSE, and (2) to give the developer the option to do
less granular locks. How about giving me the option to set a manual lock
but otherwise automat
ot;Al Musella, DPM" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Sat, 16 Sep 2000 20:57:26 -0400
> To: [EMAIL PROTECTED]
> Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
>
>
> I read that paper, and still would like to have an option for
I read that paper, and still would like to have an option for automatic
locking. Maybe add an attribute to the cfapplication tag: automatic
locking: on |off
The development time saved on it will more than offset the cost of a
faster processor needed for the 2 or 3 microseconds added t
Yes, they explained why. See Allaire's recent paper,
"ColdFusion Locking Best Practices"
http://www.allaire.com/handlers/index.cfm?ID=17318&Method=Full
best, paul
At 11:56 AM 9/16/00 -0400, you wrote:
>Why can't cold fusion just automatically lock
>them? Has Allaire ever responded on this issu
IF all reads and writes of memory variables have to be locked, why do we
have to be concerned with it? Why can't cold fusion just automatically lock
them? Has Allaire ever responded on this issue? Maybe we could all email
the request to allaire?
I have thousands of templates that were wri
At 15:12 9/15/00 -0400, you wrote:
>Yeah I thought it was agreed that all memory locking was suggested. Even in
>my presentation that I gave over a month ago I stated in there that there
>was disagreement but basically every memory variable whether written or read
>had to be locked. Ben Forta disa
15, 2000 1:08 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
> i'd disagree... if you look back over all the emails in all
> of the threads, you should see that more people only lock
> writes versus l
> i'd disagree... if you look back over all the emails in all
> of the threads, you should see that more people only lock
> writes versus locking both. that consensus by the majority
> is what i was commenting too.
You may see more emails here recommending the locking of writes only, but
that'
> The sad thing is this pretty much means that Allaire is
> admitting that the memory model in CF needs serious work.
> I'm paraphrasing of course ;) The way CF deals with memory
> in general is pretty weak. "Restart the service to release
> unused memory" is not my idea of an acceptable polic
both. that consensus by the majority is what i was commenting too.
-mike
> -Original Message-
> From: Peter Theobald
[mailto:[EMAIL PROTECTED]"
eudora="autourl">mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 13, 2000 8:30 PM
> To: [EMAIL PROTECTED]
> Subje
L PROTECTED]]
> Sent: Wednesday, September 13, 2000 8:30 PM
> To: [EMAIL PROTECTED]
> Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
>
>
> The consensus was *NEVER* that you didn't have to lock reads.
> Cold Fusion doesn't FORCE locking - it is up to you to lock
The consensus was *NEVER* that you didn't have to lock reads.
Cold Fusion doesn't FORCE locking - it is up to you to lock access to an Application
variable.
If you lock the writes but don't lock the reads, then when Cold Fusion comes upon a
read without a lock it will blindly run the read even i
s will take your and my
comments together to reach their own conclusions.
Steve
-Original Message-
From: John Cummings [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 13, 2000 7:06 PM
To: [EMAIL PROTECTED]
Subject: Re: cflocking.. -- ATTENTION -- MY CASE STUDY
Steve,
Cold Fus
You had problems reading without locking, BUT, were you possibly
writing to those variables at the same time? I was at a CF
seminar and the speaker said you do not need to lock application
variables IF YOU KNOW they will not be written to during the read.
Maybe its a datasource name thats only wri
Just my two cents.
HTH,
John Cummings
- Original Message -
From: "Steve Bernard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 13, 2000 6:41 PM
Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
> The sad thing is this pretty much means
emory left." Sounds like a CF
Server that isn't restarted on a nightly basis ;)
-Original Message-
From: Mike Amburn [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 13, 2000 6:06 PM
To: [EMAIL PROTECTED]
Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
i'v
need be.
HTH,
John Cummings
- Original Message -
From: "Mike Amburn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 13, 2000 6:05 PM
Subject: RE: cflocking.. -- ATTENTION -- MY CASE STUDY
i've been following the CFLOCK threads fo
i've been following the CFLOCK threads for months and months now. i even
started several. unfortunately, the problem is that there doesn't seem
to be any consensus on what's the end-all, be-all, definitive answer to
the question "do you have to lock reads or just writes?" now i can't
speak for any
20 matches
Mail list logo
