Hanson Char wrote: > In the SoftReference model, for example, each soft cache item gets > automatically deleted by the GC when (or before to be precise) there is not > enough memory. Each such deleted item will be placed on to a reference > queue by the GC. RCS just needs to release all resources (locally) in > relation to the cache items. It doesn't need to invalidate the cache items > on the client caches. It doesn't matter even if some client caches may > still have a copies of the deleted items, as the next change/load of a cache > item on a client cache will initiate the cycle of sychronizing of the latest > copy to both RCS and other client caches all over again.
This SoftReferenceModel you're refering to: is this the current way the remote caching works now? Or is this how it might work in the future? If so, how does it work now regarding the out-of-memory condition? Akos -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
