This does sound weird - really not sure what this has to do with
ActiveMQ
On 10 Jun 2010, at 21:54, Marnie McCormack <[email protected]
> wrote:
I'm not sure what the best solution is, but I do know that I'm
missing what
the problem using one of the Apache projects for this work is ?
It seems like there some context missing from this debate, possibly
from
discussions at the F2F.
Bruce - can you elaborate on why other people might not want to work
on AMQP
under an Apache project but would want to work on it as another open
source
project and use an ASL license ?
It seems a little like double overhead for those already working on
Qpid or
ActiveMQ to have a third project in the loop, with different lists and
process and all that. Having been around for a while I understand the
overhead with Apache, but I'm also concerned that we haven't really
talked
about what we gain from a non-Apache project - what the gain from
doing the
core libraries somewhere else ?
Regards,
Marnie
On Thu, Jun 10, 2010 at 9:28 PM, Steve Huston <[email protected]>
wrote:
-----Original Message-----
From: Gordon Sim [mailto:[email protected]]
Sent: Thursday, June 10, 2010 3:38 PM
To: [email protected]
Cc: [email protected]
Subject: Re: AMQP client library collaboration
On 06/10/2010 06:57 PM, Bruce Snyder wrote:
On Thu, Jun 10, 2010 at 5:50 PM, Gordon Sim<[email protected]>
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?
Ideally it would be great to get participation from other
AMQP-implementing groups as well.
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
