Robbie Gemmell wrote:
3. From the next release we need to ship separate binaries for the
broker, client and management bits.
We already do release separate bundles for pretty much everything (Client,
Broker, QMan[management-client], and JMX Management Consoles). From the next
release I would suggest that we stop shipping the 'java bundle' binary which
mashes most of those contents together.
I'm not really a big fan of not shipping the bundle.
I think users who OEM the client want to clearly understand what it's
dependencies are and obviously want them as minimal as possible, and I
certainly think this is an important usage scenario to accommodate,
however I think a large part of that can be achieved without having a
client-only download, and I think it's important to recognize that it's
not our only usage scenario.
Now I'm not really against having a client only download, but I do think
the bundle should be kept, and in fact should really be thought of as
the primary download for the simple reason that a client-only download
is actually quite useless to most of our prospective users because you
can't actually do anything useful with the client unless you have a
broker somewhere, and even then I doubt you'll get very far without some
management tools for simple diagnostics.
Contrast this to a download that includes the broker, the client, some
basic diagnostic/management tools, and some working examples, and I
think our potential users will have a much nicer out-of-the-box
experience with a bundle.
Granted our current bundle needs some work to live up to this, but
I don't think that's a reason to throw the baby out with the bathwater.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
