That's what I was thinking too :-)
My app fills in a huge Application structure ONCE and from then on never writes it
again.
Months later we added a page to the admin section to let the client edit some of the
information in the database that Application structure is built from. Of course when
we re-load the Application structure we have a small but real window where user's can
read from the structure in mid-build and cause nasty results. We realized it before it
caused any trouble.
I would expect that a read in that situation could get garbage data, but I don't
understand why it (reportedly) can crash the server. Why not just cause an error?
Wrong data or 'Variable undefined'?
At 11:14 PM 10/10/00 -0700, paul smith wrote:
> From what I'm told, a Read Lock is not a big performance hit.
>I fact, if you're sure your app never writes to the structure,
>you can omit the Read Lock.
>
>best, paul
>
>At 11:00 PM 10/10/00 -0700, you wrote:
>>Which method is better? For what regime does Duplicate beat CFLOCK? I
>>imagine this would be a function of the structure's complexity and of the
>>number of CFLOCK calls.
>
>------------------------------------------------------------------------------
>Archives: http://www.mail-archive.com/[email protected]/
>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.
---------------------------------------------------------------------------
Peter Theobald, Chief Technology Officer
LiquidStreaming http://www.liquidstreaming.com
[EMAIL PROTECTED]
Phone 1.212.545.1232 x204 Fax 1.212.545.0938
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
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.
