[
https://issues.apache.org/jira/browse/DIRECTMEMORY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133405#comment-13133405
]
Hudson commented on DIRECTMEMORY-16:
------------------------------------
Integrated in directmemory-trunk #32 (See
[https://builds.apache.org/job/directmemory-trunk/32/])
[DIRECTMEMORY-16] Additional fixes to non-singleton implementations.
iocanel :
Files :
*
/incubator/directmemory/trunk/directmemory-cache/src/main/java/org/apache/directmemory/cache/CacheServiceImpl.java
*
/incubator/directmemory/trunk/directmemory-cache/src/main/java/org/apache/directmemory/memory/MemoryManager.java
> Create a non Singleton MemoryStorage alternative
> ------------------------------------------------
>
> Key: DIRECTMEMORY-16
> URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-16
> Project: Apache DirectMemory
> Issue Type: Improvement
> Reporter: Raffaele P. Guidi
> Assignee: Ioannis Canellos
> Attachments: DIRECTMEMORY-16-patch.txt
>
>
> Create a non Singleton MemoryStorage alternative (it also a foundation to
> build multiple caches for the same VM).
> See the discussion in the ML with Ashish (and also Simone Tripodi brought up
> the subject before) for details
> > Ashish wrote:
> While creating a DirectMemory sample, I realized that there is no way
> to create multiple caches within same JVM.
> This is a fairly common use case, and we might need multiple caches
> with different configurations.
> On Sat, Oct 15, 2011 at 10:48 PM, Raffaele P. Guidi
> <[email protected]> wrote:
> > We can consider the current implementation as the shortest path to a working
> > and efficient off-heap cache, and I really would like to keep things this
> > simple - no configuration at at all for the default configuration - but the
> > subject of multiple buckets has been already brought up and give users a
> > choice will be great.
> >
> > Now, I like the current Cache facade as it is (it is straightforward for
> > simple use cases) but MemoryStorage should be refactored - it is probably
> > wrong to have it as a singleton (the underlying OffHeapMemoryBuffer, the
> > basic building block, is not a singleton) - and we could write a
> > non-singleton implementation for the Cache as well - and here it is the
> > implementation for multiple caches (buckets?) in the same VM.
> >
> > Then the Cache singleton facade could be rafactored to use the non singleton
> > one as its foundation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
