Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84A2217A23 for ; Tue, 31 Mar 2015 09:19:02 +0000 (UTC) Received: (qmail 40757 invoked by uid 500); 31 Mar 2015 09:18:03 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 40698 invoked by uid 500); 31 Mar 2015 09:18:03 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 40687 invoked by uid 99); 31 Mar 2015 09:18:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2015 09:18:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [217.70.183.196] (HELO relay4-d.mail.gandi.net) (217.70.183.196) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2015 09:17:57 +0000 Received: from mfilter31-d.gandi.net (mfilter31-d.gandi.net [217.70.178.162]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id B7072172197 for ; Tue, 31 Mar 2015 11:16:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter31-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter31-d.gandi.net (mfilter31-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id R+1Q3S8fNpss for ; Tue, 31 Mar 2015 11:16:55 +0200 (CEST) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.10] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id EAAD41721B0 for ; Tue, 31 Mar 2015 11:16:54 +0200 (CEST) Message-ID: <551A6606.5020403@nanthrax.net> Date: Tue, 31 Mar 2015 11:16:54 +0200 From: =?UTF-8?B?SmVhbi1CYXB0aXN0ZSBPbm9mcsOp?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: dev@activemq.apache.org Subject: Re: [PROPOSAL] Pluggable Brokers... References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org +1 Regards JB On 03/30/2015 03:23 PM, James Carman wrote: > All, > > With all the talk over the last week or so regarding the "Broker > Wars", especially after reading Rob Davies' email about how the broker > has been tweaked through the years to emphasize different aspects > (long-term storage for instance), it occurred to me that we might be > able to move past all this craziness by providing an abstraction layer > above the broker and try to make them "pluggable." > > If there really are situations where the broker needs to focus on one > particular aspect of message delivery, that sounds to me like the > "strategy" pattern. If a broker can be written in such a way that it > is allowed to focus on certain aspects and maybe ignore or completely > forego others, then it would seem to me that the code could be made > much more straight-forward, because it doesn't have to try to be the > "swiss army knife", solving everyone's problems at one time. > > Of course, this may be just a pipe dream and there's no way to do it > (admittedly I'm not terribly familiar with the code), but I thought > I'd throw it out there as a possible approach. I mean, we do this > sort of thing already with the persistence providers, so maybe there's > an opportunity here as well. > > Thoughts? > > James > --=20 Jean-Baptiste Onofr=C3=A9 jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com