Mike,
Under some circumstances, I think a lock around cfsearch is still desirable.
For example, if a user searches a collection while it is being updated
via code, then they will get an error. For this reason, we use a
readonly named lock (e.g. "AppASearchLock") around cfsearch and then
an exclusive lock with the same name ("AppASearchLock") around
<cfindex action="refresh" > for when we update the collection.
Jon
On 3/29/06, Mike Klostermeyer <[EMAIL PROTECTED]> wrote:
> I understand from the documentation that it is "no longer best practice" in
> CF7 to use cflock around cfsearch. Does this apply to CFMX a well?
>
> Mike Klostermeyer
> [EMAIL PROTECTED]
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236475
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
