Yes, this can't be stressed enough - if you don't use a read-only lock where you read the data that is elsewhere exclusively locked, then your app will happily read data while it is being written to, giving you erroneous results if it happens to occur at the right time. Read-only locks only do anything while an exclusive lock is in effect so they don't affect performance unnecessarily.
-----Original Message----- From: Adam Churvis [mailto:[EMAIL PROTECTED] Sent: Sunday, 8 May 2005 2:37 To: CF-Talk Subject: Re: High Load Server... how much more can it take? [snip] There has been a lot of talk about locking writes but not reads, but if you do this then your reads are no longer synchronized with your writes, even in the Session scope. If a resource can be involved in a race condition, lock both its writes and its reads. There is no compelling reason to not lock reads. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205983 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
