[Resend, have not seen this show up yet on the list.]
On Oct 23, 2006, at 2:08 PM, James Strachan wrote:
On 10/23/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
[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?
Yes
I think what Hiram means is that it uses the same ActiveMQ plugin
interfaces which are used to implement other protocols like OpenWire,
Stomp, XMPP (i.e. Transport and WireFormat are interfaces) - but that
it actually uses the AMQP protocol on the wire.
So, by "yes," did you mean "yes, it's non-interoperable" (which is
what I asked above), or "yes, it's interoperable" ?
In
other words, can a normal Qpid client using the AMQ protocol version
Yes - or at least thats the intention. (I've not tried it yet :)
This "yes" seems to contradict your "yes" from above, no?
I'm really not trying to be a pain, but so far responses to these
questions have been confusing. I'm just trying to make sure we're all
on the same page.
Given that ActiveMQ probably doesn't provide APIs that correspond to
AMQ features like exchanges and bindings, how is it that an ActiveMQ
application can meaningfully interact or fully interoperate with an
AMQP implementation like Qpid?
thanks,
--steve
