Great - I will to subscribe to their mailing list and try to get their attention on this
On Tue, Nov 8, 2011 at 7:32 PM, Mir Tanvir Hossain < [email protected]> wrote: > I am working part time on a project to use JCS and DirectMemory together. I > have not made much progress yet. I'd be happy to contribute my time on > integrating these projects together. > > -Mir > > On Tue, Nov 8, 2011 at 9:29 AM, Olivier Lamy <[email protected]> wrote: > > > Jcs recently had a lot of activities see > > > > > http://svnsearch.org/svnsearch/repos/ASF/search?view=resultlist&path=%2Fcommons%2Fproper%2Fjcs&plotsort=%24plotsort > > > > no release sure but some dev. > > > > 2011/11/8 Raffaele P. Guidi <[email protected]>: > > > I think the problem is the overall lack of activity in JCS. Let's try > to > > > ping them in the ml but I also would like to think about an Avro > > > distribution mechanism. The basics are very simple - sending updates to > > the > > > pointerslist to every partecipating node and asking (from node to node) > > for > > > a specific bytearray. Any volounteer for this? > > > > > > On Tue, Nov 8, 2011 at 1:30 PM, Olivier Lamy <[email protected]> wrote: > > > > > >> 2011/11/8 Raffaele P. Guidi <[email protected]>: > > >> > 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 <[email protected]> > > wrote: > > >> > > > >> >> +1 on the join idea. > > >> >> Just a matter of asking the jcs guy. > > >> >> > > >> >> 2011/11/8 Tommaso Teofili <[email protected]>: > > >> >> > I like the idea of joining forces with JCS, also, as far as I > know, > > >> since > > >> >> > 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 > > >> way > > >> >> of > > >> >> > distributing cache. > > >> >> > Just some thoughts. > > >> >> > Regards, > > >> >> > Tommaso > > >> >> > > > >> >> > > > >> >> > 2011/11/8 Mir Tanvir Hossain <[email protected]> > > >> >> > > > >> >> >> 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 > > >> caching > > >> >> >> support as well. So, the combined project could be a fantastic > > >> caching > > >> >> >> solution. > > >> >> >> > > >> >> >> -Mir > > >> >> >> > > >> >> >> On Mon, Nov 7, 2011 at 1:51 PM, Raffaele P. Guidi < > > >> >> >> [email protected]> wrote: > > >> >> >> > > >> >> >> > This is of course an interesting option - well, we could also > > >> leverage > > >> >> >> > indexed disk cache as L3 - and steal indexing and recycling > > >> >> techniques. > > >> >> >> > Merging efforts with JCS could bring to the most complete java > > >> cache > > >> >> >> > solution in the OS world. I don't have any idea about > > performance > > >> of > > >> >> JCS > > >> >> >> > and its lateral cache, but it's probably a bit outdated and > > could > > >> >> benefit > > >> >> >> > from a technology refresh (NIO, fast serialization - see > Apache > > >> Avro > > >> >> as > > >> >> >> an > > >> >> >> > example) > > >> >> >> > > > >> >> >> > On Mon, Nov 7, 2011 at 10:30 PM, Mir Tanvir Hossain < > > >> >> >> > [email protected]> wrote: > > >> >> >> > > > >> >> >> > > JCS already has distributed caching option. So, instead of > > >> >> >> > re-implementing > > >> >> >> > > the distributed cache, we can integrate tightly with JCS, > and > > >> become > > >> >> >> 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 < > > >> >> [email protected]> > > >> >> >> > > wrote: > > >> >> >> > > > > >> >> >> > > > I was looking at the jira issues and DIRECTMEMORY-13 - > Make > > >> some > > >> >> >> > > > investigation about going > > >> >> >> > > > distributed< > > >> https://issues.apache.org/jira/browse/DIRECTMEMORY-13 > > >> >> > > > >> >> >> > > > 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 > > >> not > > >> >> >> > 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 <http://fusesource.com> > > >> >> >> > > > > > >> >> >> > > > ** > > >> >> >> > > > Blog: http://iocanel.blogspot.com > > >> >> >> > > > ** > > >> >> >> > > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > > >> >> >> > > > Apache Camel <http://camel.apache.org/> Committer > > >> >> >> > > > Apache ServiceMix <http://servicemix.apache.org/> > > Committer > > >> >> >> > > > Apache Gora <http://incubator.apache.org/gora/> Committer > > >> >> >> > > > Apache DirectMemory < > > http://incubator.apache.org/directmemory/ > > >> > > > >> >> >> > > Committer > > >> >> >> > > > * > > >> >> >> > > > > > >> >> >> > > > > >> >> >> > > > >> >> >> > > >> >> > > > >> >> > > >> >> > > >> >> > > >> >> -- > > >> >> Olivier Lamy > > >> >> Talend : http://talend.com > > >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy > > >> >> > > >> > > > >> > > >> > > >> > > >> -- > > >> Olivier Lamy > > >> Talend : http://talend.com > > >> http://twitter.com/olamy | http://linkedin.com/in/olamy > > >> > > > > > > > > > > > -- > > Olivier Lamy > > Talend : http://talend.com > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > >
