[infinispan-issues] [JBoss JIRA] (ISPN-9365) Async store refresh

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604102#comment-13604102 ] 

Dan Berindei commented on ISPN-9365:
------------------------------------

I think calling the loader for expired entries and returning expired entries are orthogonal issues. 

For the latter we definitely need additional configuration, but for the former we could decide to call the loader for expired entries based on whether it's a writer as well. A store that implements both {{CacheLoader}} and {{CacheWriter}} is expected to return the entries exactly the same as they were stored, with the same metadata, but a loader is free to return a different metadata (in this case, timestamp) every time it's queried.

> Async store refresh
> -------------------
>
>                 Key: ISPN-9365
>                 URL: https://issues.jboss.org/browse/ISPN-9365
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Loaders and Stores
>            Reporter: William Burns
>
> It has been discussed we should have some sort of configuration to allow for an always not null cache. That is that it would use expiration and/or eviction to relieve memory constraints, but would have a backing store that always produced non null entries.
> It could also return expired entries and in the background recalculate the new value and replace it asynchronously. This may or may not want to be configured.
> Then any cache user could always assume that a not null entry is returned.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)