>> The name is used when you don't actually lock the
>> persistent scope
>>variables. The lock doesn't care what's in it, it just
>>single threads all
>>requests.
>
> Thanks for the clarfication, good to know, in other words,
> when NAME is used regardless of the value of NAME itself
> CF server applys "single thread" for all requests.
All requests with the same name, yes.
>> 3) given the fact that SCOPE and NAME attributes are
>> mutually exclusive,
>> use one of them would suffice, so, the question is when
>> to use SCOPE and
>>when to use NAME (data integriy number one task, less
>>memory usage second
>>for either preCFMX or CFMX)?
>>
>> [Tom Kitta]
>> Name is less used since it is not for
>> session/application/server. You can
>>use it to say single thread file access for example.
>
> I took your comment as SCOPE is preferable to NAME for
> performance sake, yes?
The rule of thumb is that properly named locks will perform better
than scope locks, however, because you have complete control over the
names, named locks can perform worse than scoped locks if the name
provided is inspecific, i.e.
<cflock scope="session">
will probably perform better than
<cflock name="session">
(assuming the same scheme is used for locking the same events
throughout the application)
on the other hand
<cflock name="#getcurrenttemplatepath()#">
will perform _much_ better than
<cflock scope="session">
s. isaac dealey 214.823.9345
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
