Ulf, Our primary goal with JMS reloaded is to address the items you highlighted. Adrian and I had a very interesting discussion about number one, and Bill and I discussed clustering a bit in SF last week. So we are certainly focused on number 1 and 2. Number 3 is less of a concern to me right now. Overall, however, our goals are certainly aligned.
I'm going to be putting together a formilized project plan next week that I'll publish on the website. From it, you and I should be able to determine where you have the time and skill to contriute the most. Thanks, Nathan Phelps JMS/JBoss (Reloaded) Project Lead JBoss Group, L.L.C. Quoting [EMAIL PROTECTED]: > Hi Nathan, > > thanks for the information. I already have seen your first CVS code. Is > there any further information available about the planed design and > feature set ? You already gave some interesting insights about the p2p > feature. When using jms in an enterprise production environment - as we > would like to do - the following aspects are of even more importance ( and > most of these isues are not handled very well in the current JBossMQ > implementation ) > > (1) EFFICIENT handling of large / high numbers of PERSISTENT topic and > queue messages > (2) message redelivery / message throttling clustering / failover > (3) messaging system monitoring / administration > > I there a way to participate in the your ongoing rewrite ? > > Regards > Ulf > > > > > "Nathan Phelps" <[EMAIL PROTECTED]> > Gesendet von: [EMAIL PROTECTED] > 15.06.2003 00:00 > Bitte antworten an jboss-development > > > An: <[EMAIL PROTECTED]> > Kopie: > Thema: RE: [JBoss-dev] JBossMQ rewrite > > > JBossMQ?the current code base?will continue to ship with JBoss 3.2 which > is, > and will remain for some time, the production version. Therefore, making > changes to the current code base IS NOT worthless. However, I am working > on > a brand new implementation with assistance from Adrian, Bela, Bill, Tom > Elrod, and Troy Daley. The framework code has recently been checked in to > the jboss-jms module in CVS. It is early, but a start. In addition to > the > traditional client-server oriented JMS we're working on, at Bela's > suggestion, I was able to implement a pure p2p implementation of the JMS > topic messaging domain that does non-durable subscribers over JavaGroups. > At Bill's request, we're going to get this code out there quickly (July). > To my knowledge this will be the first pure p2p (server-less) JMS > implementation in open source and it will provide very fast in-firewall > publish and subscribe over multicast. > > Thanks, > > Nathan Phelps > JMS/JBoss (Reloaded) Project Lead > JBoss Group, L.L.C. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Friday, June 13, 2003 4:45 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] JBossMQ rewrite > > > Can anyone give me some informations about the current state of the > announced rewrite of JBossMQ for JBoss 4 ? Does it still make sense to > implement needed features on the current JBossMQ implementation ? I don't > want to spend time on something that gets nuked in short time :-) > > Regards > Ulf > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
