As mentioned in previous mails, I am working on adding AMQP 1.0 support
for the c++ qpid::messaging client and for qpidd for the 0.20 release.
I should have an initial, basic implementation ready for review next
week and will then be working through the various limitations. The
following is a proposed schedule, but I'm interested in hearing opinions
on different prioritisation etc.
Sep 26th: Initial implementation available for review
* basic send & receive of AMQP 1.0 messages through queues/exchanges[1]
* message translation on broker between 0-10 & 1.0 formats as needed[2]
* builds against proton 0.1
At this point I'll send a mail with more detail on the mapping of the
qpid::messaging API on to the 1.0 protocol including any questions and
options.
Oct 3rd:
* support for address options in qpid::messaging (depends on PROTON-9)
* support for 'legacy filters' (i.e. pre 1.0 exchange matching) (also
depends on PROTON-9)
* make AMQP 1.0 (broker) connection, sessions and links visible through
management
Oct 10th:
* durable messaging; broker acknowledges only after async store
operation completes
* structured content messages
Oct 17th (0.20 Alpha):
* cyrus sasl integration
* SSL support for client
Limitations unlikely to be resolved in time for 0.20:
* no 1.0 based federation
* no transactions for 1.0 sessions
* no QMF over 1.0
* no support for reconnect on client
* SSL support on broker not activated through AMQP 1.0 security layer
At present I'm compiling the 1.0 support directly into both broker and
client. There are other options there. The 1.0 support could be an
optional plugin on both client and broker, on the client side there
could be two distinct libraries to link against depending on the version
required.
Thoughts, comments, opinions on this and the proposed schedule above all
welcome!
--Gordon.
[1] At present use of exchanges is limited due to lack of access to
filters. Once PROTON-9 is resolved that limitation can be addressed.
[2] This will not include any translation of the message body itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
