Vladimir and I agreed on the general API design of the distributed execution framework. To propose more concrete API with interfaces and classes, I have to create a Java package that contains them. And it means we need to name the package. :-) Anyone have a good subproject name in mind? Probably Manik might have one. :-) Cheers -- Trustin Lee - http://gleamynode.net/ _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Infinispan DExec On 9 nov. 2010, at 19:32, Manik Surtani <manik(a)jboss.org&gt; wrote: > Hmm; org.infinispan.execution? o.i.forkjoin? o.i.mapreduce? o.i.runnable? What are the names of the classes/interfaces you are proposing, and what do each of them do? That may give us a clue into picking a pkg name. > > On 9 Nov 2010, at 14:23, 이희승 (Trustin Lee) wrote: > >> Vladimir and I agreed on the general API design of the distributed >> execution framework. >> >> To propose more concrete API with interfaces and classes, I have to >> create a Java package that contains them. And it means we need to name >> the package. :-) >> >> Anyone have a good subproject name in mind? Probably Manik might have >> one. :-) >> >> Cheers >> >> -- >> Trustin Lee - http://gleamynode.net/ >> >> >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > -- > Manik Surtani > manik(a)jboss.org > Lead, Infinispan > Lead, JBoss Cache > http://www.infinispan.org > http://www.jbosscache.org > > > > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Hmm; org.infinispan.execution? o.i.forkjoin? o.i.mapreduce? o.i.runnable? What are the names of the classes/interfaces you are proposing, and what do each of them do? That may give us a clue into picking a pkg name. On 9 Nov 2010, at 14:23, 이희승 (Trustin Lee) wrote: > Vladimir and I agreed on the general API design of the distributed > execution framework. > > To propose more concrete API with interfaces and classes, I have to > create a Java package that contains them. And it means we need to name > the package. :-) > > Anyone have a good subproject name in mind? Probably Manik might have > one. :-) > > Cheers > > -- > Trustin Lee - http://gleamynode.net/ > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

I don't think it will have a separate release cycle. I actually see it being a part of infinispan-core since it is pretty close to the central concepts of distribution, etc. Maybe it could be a separate maven module (i.e., a separate jar in the distribution) but it would still follow the same release cycles and be in lock-step with the rest of Infinispan. On 10 Nov 2010, at 06:32, 이희승 (Trustin Lee) wrote: > Hmm, yeah, the package name could be rather a generic one like > org.infinispan.execution, but it will have somewhat independent release > cycle, right? I guess we need some sub-project name. > > Manik Surtani wrote: >> Hmm; org.infinispan.execution? o.i.forkjoin? o.i.mapreduce? o.i.runnable? What are the names of the classes/interfaces you are proposing, and what do each of them do? That may give us a clue into picking a pkg name. >> >> On 9 Nov 2010, at 14:23, 이희승 (Trustin Lee) wrote: >> >>> Vladimir and I agreed on the general API design of the distributed >>> execution framework. >>> >>> To propose more concrete API with interfaces and classes, I have to >>> create a Java package that contains them. And it means we need to name >>> the package. :-) >>> >>> Anyone have a good subproject name in mind? Probably Manik might have >>> one. :-) >>> >>> Cheers >>> >>> -- >>> Trustin Lee - http://gleamynode.net/ >>> >>> >>> _______________________________________________ >>> infinispan-dev mailing list >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> -- >> Manik Surtani >> manik(a)jboss.org >> Lead, Infinispan >> Lead, JBoss Cache >> http://www.infinispan.org >> http://www.jbosscache.org >> >> >> >> >> >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > -- > Trustin Lee - http://gleamynode.net/ > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev