On 07/19/2012 04:59 PM, Hiram Chirino wrote:
Well, from a ASF point of view there is some duplication of effort in maintaing a Qpid Java broker and a ActiveMQ java broker. They both target similar users (folks who like running apps on the JVM) and use cases. This situation will be even more intese once ActiveMQ implements the AMQP 1.0 spec.
Agreed.
From my point of view, and it's a VERY biased and insensitive point of view (sorry if I offend anyone):
Your point of view is very far from being insensitive so please don't be concerned at giving any offence! I asked for your opinion, and am grateful for it.
<dream> The ideal split of *Java* tech bits across the projects would be to have QPID implement all the non-broker specific libs like Proton, clients, bridges and perhaps even proxies/intermediaries. (Here's where the very biased bit comes in...) Then QPID folks then implement/maintain an AMQP java broker on using ActiveMQ's Apollo project and Qpid's non-broker specific bits. In Apollo the protocols are implemented a plugins on top of the core. You could take the Apollo distro, strip out the STOMP protocol it ships, and then slap on your AMQP implementation. So you could end up with a broker which focused on just AMQP hopefully keeping your current QPID java broker users happy.
So the idea would be to have an AMQP plugin that used proton as part of Apollo?
The current plan is for Apollo to eventually become AcitveMQ 6. ActiveMQ 6 could then continue to be the ASF's multi-protocol Java messaging broker. It would repackage Apollo + QPID's Apollo AMQP impl + Apollo's STOMP impl + ActiveMQ's current protocol impl + other bits like an MQTT protocol impl. That means Qpid's AMQP broker impl would also tag along and make it upstream into lots of other projects like ServiceMix and Apache Geronimo.
To me, at least at this high level view, that would seem to make a lot of sense and I suspect would make a lot of users happy.
The nice thing all the projects would have a nice common broker base we could collaborate on (the Apollo core). Each project could release broker distos which are focused on 1 protocol, and the ActiveMQ distro could repackage everything into one monstrous distribution where all the protocols are integrated. Naturally if something like this was to occur, the Qpid broker devs would quickly get commit rights to ActiveMQ since they will probably need to stretch and pull Apollo's broker core in new directions.
Yes, my one concern would be that we could offer 'full' AMQP support, including any extensions such as filters, or transaction coordination protocols, management mechanisms that may be defined in ongoing standards work.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
