On 25 June 2012 20:06, Justin Ross <jr...@redhat.com> wrote: > On Mon, 25 Jun 2012, Rafael Schloming wrote: > >> The fundamental issue here is that Qpid now needs to serve two >> audiences. A very horizontal audience made up of pretty much anything >> that might ever want to speak AMQP, and a more specialized, vertical >> audience of people interested in a particular message broker. > > > I accept that we have distinct audiences. I'm not, however, at ease with > binding "Qpid" to "a particular message broker" and "Proton" to the future, > and there being only two things, the old and the new. >
I don't think that is what I was saying, nor how you could reasonably draw that inference. I would be equally supportive of Rajith's suggestion of setting up a qmf list. > I'd like to see a scheme like below (beware silly made up names): > > Qpid - Qpid is a leading implementor of AMQP; it has the following > components: > > - Proton - Proton is an AMQP protocol engine for use by integrators > > - Futon - Futon is a suite of messaging APIs [built on Proton] > > - Halfton - Traditional back-office brokers [built on Proton] > > In my view, the future of Qpid should be represented under the name "Qpid" > (with the brand redefinition that implies!), and things like Proton are > understood to be components of Qpid. > > I suspect that if we don't create an agreed, understandable scheme for the > different parts, then development will go to one stream or another simply by > developer inertia. > That's not unreasonable, except Futon and Halfton don't exist yet and I'm not sure that I know enough to say those will be precisely those three things. I'm certainly very comfortable pushing everything one level below Qpid and using Qpid as the uber-brand for "AMQP @ Apache" - that is very much my vision, at least. > Already, we have the new messenger API in Proton and the messaging API in > Qpid. How did you decide where to put it? I'm not sure that that is actually decided... it was an outgrowth of Proton, but personally I'd expect it to move somewhere else within the fullness of time. At the moment I would expect it's release cycles to mirror those of the proton engine as they are both in rapid and coupled development at the moment. As things become more mature I would expect that to be decoupled. - Rob > > Justin > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
