Mailing-List: contact directmemory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: directmemory-dev@incubator.apache.org
Date: Fri, 24 Feb 2012 09:06:53 +0000 (UTC)
From: "Olivier Lamy (Updated) (JIRA)" <jira@apache.org>
To: directmemory-dev@incubator.apache.org
Message-ID: 
 <1438215088.14631.1330074413433.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <567038796.18210.1318759211889.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DIRECTMEMORY-16) Create a non Singleton
 MemoryStorage alternative
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRECTMEMORY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated DIRECTMEMORY-16:
-------------------------------------

    Fix Version/s: 0.6.0
    
> 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
>             Fix For: 0.6.0
>
>         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
> <raffaele.p.guidi@gmail.com> 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