[Sorry if this is a duplicate -- originally sent it Saturday but
haven't seen it show up here.]
On Oct 20, 2006, at 10:29 PM, Hiram Chirino wrote:
Hey Folks,
Just wanted to give you an update on the progress that ActiveMQ is
making in
supporting AMQP clients. I have taken most of the java code from
the qpid
project and done some major refactoring to it so that it's more
inline with
the ActiveMQ architecture. It now uses the ActiveMQ transport,
wireformat,
broker service, connector, and configuration patterns. So now it is
possible to have your ActiveMQ broker support both standard
ActiveMQ clients
and AMQP clients like the qpid implemented java and C++ clients.
May I ask for a clarification? If your work uses the ActiveMQ wire
format, does that mean that it's non-interoperable with Qpid? In
other words, can a normal Qpid client using the AMQ protocol version
0.8 talk directly to an ActiveMQ broker based on this work?
--steve
The stuff that still missing is that the AMQP messages are in separate
messaging domain from the ActiveMQ messages. The next set of work
that's
still pending is :
- Need to add Unit tests!
- integrating the messaging domains
- implementing the AMQP persistence using ActiveMQ's message stores
- porting the sasl implementation in qpid (big refactor needed to
make it
IOC configured).
- and once we are happy with all the integration and everything is
pretty
stable, JMXify it!
Please note that the AMQP spec is still moving so the latest qpid's
clients
may no long be compatible with this work, (I've been testing
against qpid
sources about 3 weeks old.) Hopefully qpid will do a milestone
release soon
and then I'll port the protocol changes that I've missed when they
do that.
If anybody wants to pitch in and help, here's where our amqp/qpid
integration module is located in svn:
http://svn.apache.org/viewvc/incubator/activemq/sandbox/qpid
--
Regards,
Hiram
Blog: http://hiramchirino.com
