Rafael Schloming wrote:
Rafael Schloming wrote:
The upshot is you can sort of look at these as providing a JMS-like
API plus some critically missing bits minus some extra cruft.
One thing I should say before someone accuses me of bashing our JMS
client too much is that most of the critically missing bits of
functionality are actually also available in our JMS client, just not
via the JMS API. They're usually accessible via some system property
or other.
OK, I get it now. But the naming is more AMQP-like than JMS-like, it
seems. Which is good.
As long as we separate out the configuration APIs from the messaging
APIs, this approach makes sense to me.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
