Return-Path: X-Original-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A327B9617 for ; Tue, 8 Nov 2011 12:30:29 +0000 (UTC) Received: (qmail 33385 invoked by uid 500); 8 Nov 2011 12:30:29 -0000 Delivered-To: apmail-incubator-directmemory-dev-archive@incubator.apache.org Received: (qmail 33365 invoked by uid 500); 8 Nov 2011 12:30:29 -0000 Mailing-List: contact directmemory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: directmemory-dev@incubator.apache.org Delivered-To: mailing list directmemory-dev@incubator.apache.org Received: (qmail 33357 invoked by uid 99); 8 Nov 2011 12:30:29 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2011 12:30:29 +0000 Received: from localhost (HELO mail-qw0-f47.google.com) (127.0.0.1) (smtp-auth username olamy, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2011 12:30:29 +0000 Received: by qabj40 with SMTP id j40so384891qab.6 for ; Tue, 08 Nov 2011 04:30:28 -0800 (PST) Received: by 10.50.89.227 with SMTP id br3mr51448700igb.14.1320755428053; Tue, 08 Nov 2011 04:30:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.180.200 with HTTP; Tue, 8 Nov 2011 04:30:07 -0800 (PST) In-Reply-To: References: From: Olivier Lamy Date: Tue, 8 Nov 2011 13:30:07 +0100 Message-ID: Subject: Re: Distributed DirectMemory To: directmemory-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2011/11/8 Raffaele P. Guidi : > Do someone knows them? Not personnally :-) BTW Simone is a very active commons dev. IMHO Maybe you can simply send an email to commons-dev@ ? > > On Tue, Nov 8, 2011 at 12:11 PM, Olivier Lamy wrote: > >> +1 on the join idea. >> Just a matter of asking the jcs guy. >> >> 2011/11/8 Tommaso Teofili : >> > I like the idea of joining forces with JCS, also, as far as I know, si= nce >> > it's Apache licensed we could eventually take that same code and port = it >> in >> > DM, but obviously I think we should try to avoid it. >> > Regarding the distributed cache I know Hadoop offers one so that could >> also >> > be an option for an off-heap plugin. >> > However I personally would be happy also to use NIO and have our own w= ay >> of >> > distributing cache. >> > Just some thoughts. >> > Regards, >> > Tommaso >> > >> > >> > 2011/11/8 Mir Tanvir Hossain >> > >> >> I think it would be a great idea to merge these project to create a >> >> complete caching solution. JCS seems to have an excellent disk cachin= g >> >> support as well. So, the combined project could be a fantastic cachin= g >> >> solution. >> >> >> >> -Mir >> >> >> >> On Mon, Nov 7, 2011 at 1:51 PM, Raffaele P. Guidi < >> >> raffaele.p.guidi@gmail.com> wrote: >> >> >> >> > This is of course an interesting option - well, we could also lever= age >> >> > indexed disk cache as L3 - and steal indexing and recycling >> techniques. >> >> > Merging efforts with JCS could bring to the most complete java cach= e >> >> > solution in the OS world. I don't have any idea about performance o= f >> JCS >> >> > and its lateral cache, but it's probably a bit outdated and could >> benefit >> >> > from a technology refresh (NIO, fast serialization - see Apache Avr= o >> as >> >> an >> >> > example) >> >> > >> >> > On Mon, Nov 7, 2011 at 10:30 PM, Mir Tanvir Hossain < >> >> > mir.tanvir.hossain@gmail.com> wrote: >> >> > >> >> > > JCS already has distributed caching option. So, instead of >> >> > re-implementing >> >> > > the distributed cache, we can integrate tightly with JCS, and bec= ome >> >> its >> >> > > off-heap plugin. So, JCS could be the L1 cache, and DirectMemory >> could >> >> be >> >> > > the L2 cache. Just an idea. >> >> > > >> >> > > -Mir >> >> > > >> >> > > On Mon, Nov 7, 2011 at 12:30 PM, Ioannis Canellos < >> iocanel@gmail.com> >> >> > > wrote: >> >> > > >> >> > > > I was looking at the jira issues and DIRECTMEMORY-13 - Make som= e >> >> > > > investigation about going >> >> > > > distributed> > >> >> > > > caught >> >> > > > my attention. >> >> > > > >> >> > > > I've read about some of the initial thoughts about reusing >> features >> >> of >> >> > > > existing Caches (Hazelcast or Terracotta) but I don't like this >> idea >> >> so >> >> > > > much. >> >> > > > We could reuse some of the ides that existing projects use, but= I >> >> think >> >> > > > that we should either build it on our own, or use a solution no= t >> >> > coupled >> >> > > to >> >> > > > an existing cache. >> >> > > > >> >> > > > So what are your thought about making direct memory distributed= ? >> >> > > > Any thoughts about the consistency model, discovery etc? >> >> > > > >> >> > > > -- >> >> > > > *Ioannis Canellos* >> >> > > > * >> >> > > > FuseSource >> >> > > > >> >> > > > ** >> >> > > > Blog: http://iocanel.blogspot.com >> >> > > > ** >> >> > > > Apache Karaf Committer & PMC >> >> > > > Apache Camel Committer >> >> > > > Apache ServiceMix =A0Committer >> >> > > > Apache Gora Committer >> >> > > > Apache DirectMemory >> >> > > Committer >> >> > > > * >> >> > > > >> >> > > >> >> > >> >> >> > >> >> >> >> -- >> Olivier Lamy >> Talend : http://talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> > --=20 Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy