On 03/24/2011 09:42 AM, Robert Godfrey wrote:
All,
As we are now reaching the end of the 0.10 release process, I think it's
probably an opportune moment to look at the goals of the Qpid project for
the rest of 2011 and beyond.
As many of you are no doubt aware, I have been spending the majority of my
time over the last years on the AMQP 1-0 standard, which we can shortly
expect to be released in its final form. In advance of this I think we need
to be planning on how we are going to adapt Qpid so that AMQP 1-0 becomes
its primary protocol.
What are people's views about how we approach this?
Cheers,
Rob
I think one of the most important factors to consider is how we build
out protocol support in a way that avoids some of the significant
maintainability issues we’ve had with our previous approach. It’s pretty
clear that one of our primary pain points has been with client support.
The practice of transcoding wholesale from one client language into
another has resulted in a significant number of write-only
implementations that have proven impractical to maintain.
IMHO, one of the key elements of our 1-0 strategy going forward has to
be to share the minimum possible number of protocol implementations
between as many different client and broker environments as possible.
This goal has in fact been a key principle in the design of the 1-0
version of the protocol. Its symmetry and layering is specifically
designed to allow for the majority of the protocol machinery to be
encapsulated within a single transport layer with a simple interface
that can be embedded within a wide variety of environments.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
