2008/10/1 Arnaud Simon <[EMAIL PROTECTED]>: > >> > The assumption was that Qman is a client that implements the >> management protocol. >> > Now nothing prevent us to move the JMX specific code into java/tool >> but the management client itself can live into java/client. >> >> My 2p/€0.024/$0.036: I think java/client should be the AMQP client >> library, and things built on top of that should live elsewhere. > > This then depends on how you consider the management protocol. If you believe > that it'll be eventually part of AMQP then an implementation of it can be > located into java/client. Alternatively if you consider it as being a pure > Qpid addin then it should be hosted under /java/tool.
I'd say management is always an additional item to a protocol. I would be surprised if the majority of users want to do more than use AMQP to send messages, so we should strive to keep the client as minimal as possible to achieve that. I have no issue with additional libraries that a client can use to augment their application. I don't really see how management functionality could ever be part of the core client library. Martin -- Martin Ritchie
