[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1342) Support for Near-Cache Pattern

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-1342:
--------------------------------

      Fix Version/s: 5.1.0.ALPHA1
                     5.1.0.FINAL
    Forum Reference: http://community.jboss.org/thread/166993  (was: http://community.jboss.org/thread/166993)


> Support for Near-Cache Pattern
> ------------------------------
>
>                 Key: ISPN-1342
>                 URL: https://issues.jboss.org/browse/ISPN-1342
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Distributed Cache
>    Affects Versions: 5.0.0.FINAL
>            Reporter: Peter Novak
>            Assignee: Manik Surtani
>             Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL
>
>
> Please create some support for near-cache pattern for distributed cache. Some detailed description could be found in Oracle Coherence documentation http://download.oracle.com/docs/cd/E13924_01/coh.340/e13819/nearcache.htm  or in Cameron Purdy presentation http://frech.info/themen/CameronPurdy-DistributedCachingEssentialLessons.pdf
> It is based on combination of L1 caching in local JVM of application with combination of L2 cache based on distributed cache cluster on other servers. I tried to implement this myself, but HotRod does not support Client-side listeners (The UnsupportedOperationException is thrown).  It could be cool, if I could register some kind of eviction listener on client side and use it for invalidation of records in local cache based on event from remote distributed cache (L2). 
> Some kind of workaround was described in http://community.jboss.org/thread/166993 : "We don't have L1s yet, but you could implement Cache Listeners on the server side and use JMS to notify your clients and build an L1 that way."
> Thanks for so great cache like infinispan is. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira