putFromLoad
has the potential to store stale data, since the data may have been removed from the database and the cache between the time when the data was read from the database and the actual call to putFromLoad
. The expected usage of this class by a thread that read the cache and did not find data is:
false
, the thread should not cache the data; only if above returns true
, put data in the cache and... The expected usage by a thread that is taking an action such that any pending putFromLoad
may have stale data and should not cache it is to either call
This class also supports the concept of "naked puts", which are calls to {@link #acquirePutFromLoadLock(Object)} without a preceding {@link #registerPendingPut(Object)}call.
@author Brian Stansberry @version $Revision: $putFromLoad
has the potential to store stale data, since the data may have been removed from the database and the cache between the time when the data was read from the database and the actual call to putFromLoad
. The expected usage of this class by a thread that read the cache and did not find data is:
false
, the thread should not cache the data; only if above returns true
, put data in the cache and... The expected usage by a thread that is taking an action such that any pending putFromLoad
may have stale data and should not cache it is to either call
This class also supports the concept of "naked puts", which are calls to {@link #acquirePutFromLoadLock(Object)} without a preceding {@link #registerPendingPut(Object)}call.
@author Brian Stansberry @version $Revision: $
|
|