On 09/15/2009 10:42 PM, Andrew Wright wrote:
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.
The c++ broker uses the 'qpid management framework' (QMF) which involves sending formatted messages representing various management requests to a special exchange in the broker. The client can also get results, and details/stats of managed entities sent back as formatted messages.
At present creation and deletion of queues and exchanges isn't a actually supported over that interface, but I think it could be added fairly easily. That would give a uniform mechanism for all kinds of configuration and stats gathering.
QMF has its own API. Ideally, in the future, it will also be easy to perform operations using the messaging APIs simply by sending to (and receiving from) a special address, using a defined message schema.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
