Primary source modules

Each of these modules would have an isolated source location and an independent release cycle.

qpid-proton (existing)
qpid-dispatch (existing)
qpid-jms (existing)
qpid-python (proposed)

The main change here is the merging of the pure-Python client code and the test code.  These are already very intimately linked: "qpid-python-test" currently lives in the python subtree, and the pre-1.0 tests use the old Python client.

In effect, this changes the focus of the qpid-python module from being a messaging API to being a legacy test suite for AMQP versions before 1.0.  The current API would remain, but future effort for Python APIs would go into the wrapped C++ Messaging and Proton APIs, which support AMQP 1.0.

qpid-cpp (proposed)

The change here is moving Python QMF and related tools with the C++ code.  These are generally tightly coupled to the C++ broker.  Future management work will be achieved not via QMF but instead using the AMQP Management specification.

In the future, it may be attractive to move the messaging API into its own module.

qpid-java (proposed)

It is anticipated that eventually, the java broker will be split from (what will become) the legacy Java client (0-8..0-10).  These will become two separate nodes at the top of the tree.  At that point a move to git will be considered.

java-qmf (proposed)

 

Refactored modules

Potential future additions

Previous discussion