On 03/24/2011 10:43 AM, Robert Godfrey wrote:
So - obviously we need to hear a few more voices on this... But personally
I'm *really* keen to get the project moving towards AMQP 1-0 ASAP. In my
spare time I've sort of hacked up an AMQP 1-0 Java client, and then spliced
that onto the Qpid Java Broker... It's not code I would really consider
putting into Qpid, but this (and the code you've got on github) may be able
to help us bootstrap testing our 1-0 efforts.
If we follow the idea of the common transport, I would guess that the best
way to progress this is probably to create a branch where we can start out
defining and implementing this transport as a standalone entity. It doesn;t
seem to make sense to me to have this in trunk and tie it into the release
cycles of the current Qpid work...
Thoughts?
For developing the transport itself, I'm not sure it matters much
whether we branch or not if we're treating it as an independent
component. Obviously if we start integrating it into other pieces then a
branch for those pieces would be called for. The release cycle question
is certainly interesting. I agree it shouldn't really be tied to the
trunk release in one sense, but I do think it would be good to have
something ready for this year's ApacheCon, and given that it might make
sense to have deliverable milestones that coincide with the trunk
releases purely as a means of focusing progress.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
