activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Snyder <>
Subject Re: AMQP client library collaboration
Date Thu, 10 Jun 2010 20:00:23 GMT
On Thu, Jun 10, 2010 at 7:37 PM, Gordon Sim <> wrote:
> On 06/10/2010 06:57 PM, Bruce Snyder wrote:
>> On Thu, Jun 10, 2010 at 5:50 PM, Gordon Sim<>  wrote:
>>> On 06/10/2010 06:21 PM, Rajith Attapattu wrote:
>>>> This effort needs to be vendor neutral to encourage participation from
>>>> a wider audience, as such it's not appropriate to host in under Qpid
>>>> or ActiveMQ.
>>> What do you mean by 'vendor neutral'? How are either Qpid or ActiveMQ
>>> 'vendors'? They are surely open source projects, collaborations that both
>>> aim to be as inclusive as possible.
>> Good point, Gordon ;-). Well, I guess my thought is that because each
>> project will provide a broker implementation of the AMQP spec that
>> neither is appropriate for a neutral protocol level client that is not
>> specific to either broker. The Apache Commons HTTP Client could have
>> been hosted as a subproject to the HTTPD server project, but that
>> wasn't appropriate so it was made a separate project. The same logic
>> applies in this case.
> I would respectfully disagree. The httpd project started specifically as a
> web server (not a browser, not a generic client). The Qpid project was
> specifically started as a place for collaborating on multi language AMQP
> implementations (including but not restricted to broker code).
> Qpid should be open and inclusive, if it is not perceived as such we want to
> change that. What is it that makes 'neutrality' an issue, especially between
> two Apache projects?

I doubt that folks from other AMQP broker impls would come to the Qpid
project to work on a client. That's the point.

perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"

ActiveMQ in Action:

View raw message