On May 18, 2008, at 6:05 AM, Alex Mizrahi wrote:
IE> If you use the discipline of using with-caching before the first
read
IE> of a cached instance's slot inside with-transaction, then you
get the
IE> following cool behavior in a multi-threaded scenario:
IE> - txn one reads the cached value
IE> If you use the discipline of using with-caching before the first read
IE> of a cached instance's slot inside with-transaction, then you get the
IE> following cool behavior in a multi-threaded scenario:
IE> - txn one reads the cached values (setting read locks)
IE> - txn one does various ops in
As a quick study, I'm prototyping the following model for cached
slots. Turns out to be fairly easy to implement.
Objects that have cached slots have an extra boolean that indicates
whether the cached slots are caching or not. When you turn on
caching, all read writes are strictly to memo
