On 15 Sep 2009, at 21:57, James Mansion wrote:
Jonathan Robie wrote:
In the languages besides Java, there is no standard messaging API
to fall behind. I'll say something more on Java in a separate
message.
If its market share of deployed MOM components that lie strangely
unused, its MSMQ.
If market share of paid-for MOM matters, isn't MQSeries effectively
a de-facto standard?
But as I've said before, last time I checked the MQSeries API really
only worked in threaded clients.
James
From an MQSeries point of view it seems like IBM have been moving
towards a more JMS-like API for their non-java clients, particularly
as of version 7.
From a pure layman's perspective on JMS, we've successfully been
using JMS clients with qpid for both basic (pub/sub, point to point)
and more advanced (LVQ) operations. This would appear to bode well for
its flexibility from a messaging point of view.
The main need we've run across for a lower level java api comes from
performing administrative functions from code - a standardised admin
api would certainly be useful (cf. MQSeries PCF). I'm not sure there
would be much benefit from shoehorning this into either JMS or a
messaging api though.
Cheers,
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
